from:"WinEunuchs2Unix"

[Touch-packages] [Bug 257135] Re: notify-send(1) can't replace an existing notification

2020-12-31 Thread WinEunuchs2Unix

I ended up using the answer in Ask Ubuntu:
https://askubuntu.com/a/871207/307523

The basic concept is you link your message to the last message you sent
with an extra line:

 -h string:x-canonical-private-synchronous:anything

Where 'anything' is the string/text grouping your spamming bubbles
together so fast repeating one replaces the one before (in that same
group).

Code snippet from within larger while loop:

GetVolume
CurrVolume="$?"
# echo CurrVolume: $CurrVolume LastVolume: $LastVolume

if [[ "$CurrVolume" != "$LastVolume" ]] ; then
# Ask Ubuntu: https://askubuntu.com/a/871207/307523
notify-send --urgency=critical "tvpowered" \
-h string:x-canonical-private-synchronous:volume \
--icon=/usr/share/icons/gnome/48x48/devices/audio-speakers.png \
"Volume: $CurrVolume"
LastVolume=$CurrVolume
VolumeCnt=10
# TODO: Process VolumeCnt internally in loop instead of larger loop
fi

if [[ $VolumeCnt > 0 ]]; then
(( VolumeCnt-- ))
SleepTime=.01
else
SleepTime=2.5
fi

sleep $SleepTime

In the link comments point out how this only works in Ubuntu and not in
Gnome. It works fine in Ubuntu 16.04.7 LTS with Unity desktop but I
haven't tried it on other desktops yet

SleepTime of '0.01' is too small for real time but the bash script has
overhead of communicating to TV over WiFi which gives it about the '0.5'
seconds lag.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/257135

Title:
  notify-send(1) can't replace an existing notification

Status in libnotify package in Ubuntu:
  Confirmed
Status in libnotify package in Debian:
  New

Bug description:
  Binary package hint: libnotify-bin

  Ubuntu 8.04, libnotify-bin 0.4.4-3build1.

  notify-send(1) is very useful but it doesn't tell me the notification
  ID that's been created, nor does it let me specify that to replace an
  earlier notification.  See http://www.galago-
  project.org/specs/notification/0.9/x408.html#command-notify, in
  particular the replaces_id parameter and the return value.

  I'd like to be able to use it something like

  id=$(notify-send --show-id foo)
  sleep 60
  notify-send --replace $id bar

  This would be great for long-running shell scripts that are monitoring
  something.

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

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

[Touch-packages] [Bug 257135] Re: notify-send(1) can't replace an existing notification

2020-12-30 Thread WinEunuchs2Unix

It would be nice to have the patch applied both the standard call from
bash as well as the python libraries (2.7.12 and 3.x).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/257135

Title:
  notify-send(1) can't replace an existing notification

Status in libnotify package in Ubuntu:
  Confirmed
Status in libnotify package in Debian:
  New

Bug description:
  Binary package hint: libnotify-bin

  Ubuntu 8.04, libnotify-bin 0.4.4-3build1.

  notify-send(1) is very useful but it doesn't tell me the notification
  ID that's been created, nor does it let me specify that to replace an
  earlier notification.  See http://www.galago-
  project.org/specs/notification/0.9/x408.html#command-notify, in
  particular the replaces_id parameter and the return value.

  I'd like to be able to use it something like

  id=$(notify-send --show-id foo)
  sleep 60
  notify-send --replace $id bar

  This would be great for long-running shell scripts that are monitoring
  something.

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

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

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

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

[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors

2019-10-20 Thread WinEunuchs2Unix

It would be easier to delete comment #10 but I can't. `zeitgeist` wasn't
resetting screen brightness and gamma. It was simply logging error it
didn't know about application I was running to reset brightness and
gamma based on time of day.

I posted a solution to getting rid of zeitgeist error messages for
`~/Desktop/*.desktop` applications which zeitgeist understandably knows
nothing about:

- https://askubuntu.com/a/1182396/307523

In summary, open Gnome Activity Log Manager / Unity Security and
Privacy. Add the directory `~/Desktop` to the blacklist.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeitgeist in Ubuntu.
https://bugs.launchpad.net/bugs/1486445

Title:
  Lots of zeitgeist errors

Status in Zeitgeist Datahub:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt"
 was not found, exec: google-chrome-stable, mime_type: application/pkix-cert
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" 
was not found, exec: google-chrome-stable, mime_type: 
application/x-extension-html
  ...
  Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop
  Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 
2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop]
  ...
  Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop

  Any clues how to fix all that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions

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

[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors

2019-10-20 Thread WinEunuchs2Unix

Received error on Ubuntu 16.04.6 LTS this morning. I've never noticed it
impacting me before but this time it reset my night time screen settings
to full daylight setting.

Results of `journalctl -xe | grep eyesome`:

Oct 19 21:40:55 alien eyesome[25582]: Wakeup: Creating 
/tmp/eyesome-is-suspending
Oct 20 05:21:17 alien eyesome[25788]: Wakeup: Called from suspend.
Oct 20 05:21:28 alien eyesome[26826]: Daemon: Resuming: Slept 2 seconds x 5 
times.
Oct 20 05:21:28 alien eyesome[26829]: Daemon: Removed file: 
/tmp/eyesome-is-suspending
Oct 20 05:29:52 alien eyesome[10076]: Sun Times: 
https://www.timeanddate.com/sun/canada/edmonton.
Oct 20 05:30:06 alien org.gnome.zeitgeist.SimpleIndexer[2098]: ** 
(zeitgeist-fts:4341): WARNING **: Unable to get info on 
application://eyesome-cfg.desktop
Oct 20 05:30:13 alien sudo[11668]: rick : TTY=unknown ; PWD=/home/rick ; 
USER=root ; COMMAND=/usr/local/bin/eyesome-cfg.sh
Oct 20 05:30:19 alien eyesome[12296]: Wakeup: Called from eyesome-cfg.sh.

Last night:
21:40:55 system suspends normally.

This morning:
05:21:17 system resumes normally.
05:29:52 cron.daily gets sunrise and sunset times from internet.
05:30:06 zeitgeist.SimpleIndexer error sets screen brightness & gamma to full.
05:30:13 I have to open ~/Desktop/eyesome-cfg.desktop with sudo.
05:30:19 I have to trigger eyesome wakeup to set screens based on time.

Possible Resolutions:
- All kinds of links on web and in Ask Ubuntu on removing zeitgeist.
- I have no need for speed improvements gained by removing.
- Suggestions that removing will break nautilus and gedit is a deal breaker.
- I would rather find out how to configure zeitgeist to play nicely with my 
data.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeitgeist in Ubuntu.
https://bugs.launchpad.net/bugs/1486445

Title:
  Lots of zeitgeist errors

Status in Zeitgeist Datahub:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt"
 was not found, exec: google-chrome-stable, mime_type: application/pkix-cert
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" 
was not found, exec: google-chrome-stable, mime_type: 
application/x-extension-html
  ...
  Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop
  Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 
2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop]
  ...
  Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** 
(zeitgeist-fts:26260): WARNING **: Unable to get info on 
application://gnome-terminal-server.desktop

  Any clues how to fix all that?

To manage notifications about this bug go to:
https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions

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

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

2018-10-07 Thread WinEunuchs2Unix

I was checking for my own log messages I was writing and found this:

$ journalctl -b | grep eyesome | grep ureadahead
Oct 07 11:15:25 alien ureadahead[289]: ureadahead:acpi-lid-event-eyesome: 
Ignored relative path

I found this bug report and ran the recommended check:

$ journalctl -b | grep ureadahead | grep relative | wc -l
6474

As I have multi-boot logging enabled I did some percentage tests:

$ time journalctl | grep ureadahead | grep relative | wc -l
14875

real0m8.072s
user0m7.991s
sys 0m3.153s

$ journalctl | wc -l
907683
$ journalctl -b | wc -l
10504

For all boots ureadahead spam is 14875/907683=1.63% of all lines
For current boot ureadahead spam is 6674/10504=63.53% of all lines

I went back through all boot logs:

$ for i in $(seq 1 145); do journalctl -b-$i | grep ureadahead | grep
relative | wc -l ; done

Booting 135 times ago also had ureadahead spam:

$ journalctl -b-135 | grep ureadahead | grep relative | wc -l
3751
$ journalctl -b-135 | head
-- Logs begin at Sat 2018-08-04 14:57:01 MDT, end at Sun 2018-10-07 11:31:03 
MDT. --
Aug 06 10:35:39 alien systemd-journald[299]: Runtime journal 
(/run/log/journal/) is 8.0M, max 78.4M, 70.4M free.
Aug 06 10:35:39 alien kernel: microcode: microcode updated early to revision 
0xc2, date = 2017-11-16
Aug 06 10:35:39 alien kernel: random: get_random_bytes called from 
start_kernel+0x42/0x50d with crng_init=0
Aug 06 10:35:39 alien kernel: Linux version 4.13.0-36-generic 
(buildd@lgw01-amd64-033) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.9)) #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 
(Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13)
Aug 06 10:35:39 alien kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=b40b3925-70ef-447f-923e-1b05467c00e7 ro noplymouth fastboot kaslr 
acpiphp.disable=1 vt.handoff=7 i915.enable_guc_loading=1 
i915.enable_guc_submission=1
Aug 06 10:35:39 alien kernel: KERNEL supported cpus:
Aug 06 10:35:39 alien kernel:   Intel GenuineIntel
Aug 06 10:35:39 alien kernel:   AMD AuthenticAMD
Aug 06 10:35:39 alien kernel:   Centaur CentaurHauls

If someone wants more journalctl details I'd be happy to provide.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1579580

Title:
  ureadahead reports relative path errors in journalctl output

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  ureadahead reports relative path errors in my journalctl output.

  This is currently 4368 lines of useless annoyances in my logs.

  To see if you have this problem, run: journalctl -b | grep ureadahead
  | grep relative | wc -l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ureadahead 0.100.0-19
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  8 15:55:18 2016
  InstallationDate: Installed on 2016-04-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160325)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-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

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

[Touch-packages] [Bug 706565] Re: configs with dots in file name not working in /etc/cron.d

2018-03-29 Thread WinEunuchs2Unix

I have multiple files with the same names that serve different purposes.
I need to differentiate them with extensions of `.sh`, `.cron` and
`.sysd` so the `locate` command returns sane results. If I have to use
`/etc/cron.d/myfile-cron` it spoils the file extension naming convention
with `/usr/local/bin/myfile.sh` and `/lib/systemd/system-
sleep/myfile.sysd`.

As per Ask Ubuntu question today:
https://askubuntu.com/questions/1020411/file-naming-conventions-for-
cron-and-systemd-extensions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/706565

Title:
  configs with dots in file name not working in /etc/cron.d

Status in cron package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cron

  I configured cron jobs with config file:
/etc/cron.d/job.cron
  and it not working.
  I spend couple of hours to understand the problem.
  Fix is to rename file withowt dots in the name:
/etc/cron.d/job
  is working.
  Renaming back to job.cron or other name with the dot in the name cause cron 
to not read this file.
  I just switched to Ubuntu Server from Fedora and it works before on those 
distributive.
  I can't find any error messages in syslog event with -L9 command line in cron 
daemon.
  I can't find any warning in man page or readme document about file names.

  I think there are 2 possible ways to fix this:
  1) put a WARNING about file names with dots (like "myjob.cron") in manpage;
  2) make cron working with those files as other distro do (ex. Fedora)

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

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

Re: [Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

2018-02-12 Thread WinEunuchs2Unix

I'm not sure of the ramifications of these error messages but I can
confirm they are still there.

On Mon, Feb 12, 2018 at 8:35 AM, Norman Henderson  wrote:
> Ladies and Gentlemen, The technical stuff is way over my head but I am
> getting the same syslog errors and the same inconsistent device paths on
> an HP Proliant ML110 G7 with Ubuntu 16.04.3 kernel 4.4.0-98-generic.
>
> It seems clear that no-one is taking ownership of this to fix it in an
> actual update that ordinary people like me can install in the normal
> course of system updates. The nature of open source software I guess.
>
> However could someone please let me know:
>  - is this just an annoying message that won't be fixed, or are there 
> operational implications?
>  - if there are implications, are they serious?
>  - if they are serious, could you explain (or point me at a resource that 
> explains) in detail, how to install the patch provided. I've never done that 
> before.
>
> Thank you in advance!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1611945
>
> Title:
>   /dev/disk/by-path not properly populated for (e)SATA port multiplier
>   disks
>
> Status in systemd package in Ubuntu:
>   Confirmed
>
> Bug description:
>   We have a just-installed Ubuntu 16.04 LTS machine with a number of
>   disks behind port-multiplier eSATA ports, all of them driven by a SiI
>   3124 controller (sata_sil24 kernel driver). Our machine sees all disks
>   on all channels, however under 16.04 only one disk from each channel
>   shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id
>   and /dev/disk/by-uuid). For our usage this is a severe defect because
>   we rotate disks in and out of the external enclosure and rely on
>   mounting specific slots in the external enclosure through /dev/disk
>   /by-path.
>
>   This did not happen in Ubuntu 12.04 LTS, the release that this machine
>   was previously running.
>
>   According to 'udevadm info --export-db' and 'udevadm test-builtin
>   path_id' and so on, systemd's udev stuff is assigning all drives
>   behind the same port the same disk/by-path data (ID_PATH et al). In
>   'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show
>   a difference in the target portion of PCI path, eg:
>
> P: 
> /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
> P: 
> /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb
>
>   However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH'
>   portions do not. For both devices above, we see:
>
> S: disk/by-path/pci-:02:00.0-ata-1
> E: ID_PATH=pci-:02:00.0-ata-1
>
>   Naturally only one device can have a /dev/disk/by-
>   path/pci-:02:00.0-ata-1 symlink, so instead of four disks per
>   channel in /dev/disk/by-path we see one.
>
>   Ubuntu release: 16.04
>
>   Package versions from 'apt-cache policy udev systemd':
>   udev:
> Installed: 229-4ubuntu7
>   systemd:
> Installed: 229-4ubuntu7
>
>   'journalctl -b' reports that during boot systemd does report some
>   'appeared twice with different sysfs paths' notes, eg:
>
>   Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath-
>   pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by
>   \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared
>   twice with different sysfs paths
>   
> /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:3:0/0:3:0:0/block/sdd/sdd1
>   and
>   
> /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
>
>   However it doesn't seem to be reporting this for all port-multiplier
>   drives and their partitions.
>
>   If it would be useful I can attach full 'udevadm info --export-db'
>   output or the like.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1611945

Title:
  /dev/disk/by-path not properly populated for (e)SATA port multiplier
  disks

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  We have a just-installed Ubuntu 16.04 LTS machine with a number of
  disks behind port-multiplier eSATA ports, all of them driven by a SiI
  3124 controller (sata_sil24 kernel driver). Our machine sees all disks
  on all channels, however under 16.04 only one disk from each channel
  shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id
  and /dev/disk/by-uuid). For our usage this is a severe defect because
  we rotate disks in and out of the external enclosure and rely on
  mounting specific slots in the external enclosure through /dev/disk
  /by-path.

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-13 Thread WinEunuchs2Unix

Complement to #56, Ubuntu 16.04.3, Kernel 4.14.4, journalctl -b:

Dec 13 20:44:33 alien bluetoothd[928]: Failed to obtain handles for "Service 
Changed" characteristic
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register 
service
Dec 13 20:44:33 alien bluetoothd[928]: Error adding Link Loss service
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register 
service
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register 
service
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register 
service
Dec 13 20:44:33 alien bluetoothd[928]: Current Time Service could not be 
registered
Dec 13 20:44:33 alien bluetoothd[928]: gatt-time-server: Input/output error (5)
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register 
service
Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register 
service

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349

Title:
  15:10 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl restart bluetooth

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

2017-12-13 Thread WinEunuchs2Unix

This bug effects 128 people and closing it because you don't like the
title feels wrong. Two Ask Ubuntu questions point to this Lanuchpad bug
report in the hopes it will be solved:

https://askubuntu.com/questions/757396/bluetooth-how-to-solve-not-
enough-free-handles-to-register-service-error

and

https://askubuntu.com/questions/773629/16-04-bluetooth-error-not-enough-
free-handles-to-register-service

A Debian bug report suggests a solution by using -E (experimental)
parameter on the systemd service exec doesn't work for Ubuntu 16.04,
Kernel 4.14.4: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949

When a hundred reported people are effected by "Not enough free handles
to register service" and you don't want to look at it because the bug
title isn't right, why not simply change the title?

Something else to consider are the thousands of people effected by
bluetooth connection problems, re-pairing, etc. What if the root of
their problems was this bug that you don't want to look at?

** Bug watch added: Debian Bug tracker #813949
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490349

Title:
  15:10 and 16.04: bluetoothd "Failed to start discovery:
  org.bluez.Error.NotReady" after bluetoothd restarted

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl restart bluetooth

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Touch-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 Ubuntu
Touch seeded 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/~touch-packages

[Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

2017-12-13 Thread WinEunuchs2Unix

Just to confirm this year old bug is still around. Ubuntu 16.04.3,
Kernel 4.14.4, NVMe Gen 3.0 x 4 M.2 SSD + Legacy 1 TB spinner, 3 NTFS-3G
mounts: /mnt/c/, /mnt/d, /mnt/e defined in /etc/fstab.

3 Errors, with 2 info lines in between, reported by `journalctl -b`:


Dec 13 05:52:20 alien systemd[1]: dev-disk-by\x2dpartlabel-
Microsoft\x5cx20reserved\x5cx20partition.device: Dev dev-disk-by
\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared
twice with different sysfs paths
/sys/devices/pci:00/:00:1d.0/:3e:00.0/nvme/nvme0/nvme0n1/nvme0n1p3
and
/sys/devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda2

Dec 13 05:52:20 alien systemd[1]: dev-disk-by\x2dpartlabel-
Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-
Basic\x5cx20data\x5cx20partition.device appeared twice with different
sysfs paths
/sys/devices/pci:00/:00:1d.0/:3e:00.0/nvme/nvme0/nvme0n1/nvme0n1p4
and
/sys/devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda3

Dec 13 05:52:20 alien systemd[1]: Found device HGST_HTS721010A9E630
HGST_Win10.

Dec 13 05:52:20 alien systemd[1]: Mounting /mnt/d...

Dec 13 05:52:20 alien systemd[1]: dev-disk-by\x2dpartlabel-
EFI\x5cx20system\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel-
EFI\x5cx20system\x5cx20partition.device appeared twice with different
sysfs paths
/sys/devices/pci:00/:00:1d.0/:3e:00.0/nvme/nvme0/nvme0n1/nvme0n1p2
and
/sys/devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda1


Parition Information from `lsblk`
=
NAMEFSTYPE LABELMOUNTPOINT   SIZE MODEL
sda931.5G HGST HTS721010A9
├─sda4  ntfs   WINRETOOLS450M 
├─sda2   128M 
├─sda5  ntfs   Image11.4G 
├─sda3  ntfs   HGST_Win10   /mnt/d   919G 
└─sda1  vfat   ESP   500M 
nvme0n1  477G Samsung SSD 960 PRO 512GB 
├─nvme0n1p5 ext4   NVMe_Ubuntu_16.0 /   44.6G 
├─nvme0n1p3   16M 
├─nvme0n1p1 ntfs 450M 
├─nvme0n1p6 swap   Linux Swap   [SWAP]   7.9G 
├─nvme0n1p4 ntfs   NVMe_Win10   /mnt/c 414.9G 
├─nvme0n1p2 vfat/boot/efi 99M 
└─nvme0n1p7 ntfs   Shared_WSL+Linux /mnt/e 9G

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1611945

Title:
  /dev/disk/by-path not properly populated for (e)SATA port multiplier
  disks

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  We have a just-installed Ubuntu 16.04 LTS machine with a number of
  disks behind port-multiplier eSATA ports, all of them driven by a SiI
  3124 controller (sata_sil24 kernel driver). Our machine sees all disks
  on all channels, however under 16.04 only one disk from each channel
  shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id
  and /dev/disk/by-uuid). For our usage this is a severe defect because
  we rotate disks in and out of the external enclosure and rely on
  mounting specific slots in the external enclosure through /dev/disk
  /by-path.

  This did not happen in Ubuntu 12.04 LTS, the release that this machine
  was previously running.

  According to 'udevadm info --export-db' and 'udevadm test-builtin
  path_id' and so on, systemd's udev stuff is assigning all drives
  behind the same port the same disk/by-path data (ID_PATH et al). In
  'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show
  a difference in the target portion of PCI path, eg:

P: 
/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
P: 
/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb

  However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH'
  portions do not. For both devices above, we see:

S: disk/by-path/pci-:02:00.0-ata-1
E: ID_PATH=pci-:02:00.0-ata-1

  Naturally only one device can have a /dev/disk/by-
  path/pci-:02:00.0-ata-1 symlink, so instead of four disks per
  channel in /dev/disk/by-path we see one.

  Ubuntu release: 16.04

  Package versions from 'apt-cache policy udev systemd':
  udev:
Installed: 229-4ubuntu7
  systemd:
Installed: 229-4ubuntu7

  'journalctl -b' reports that during boot systemd does report some
  'appeared twice with different sysfs paths' notes, eg:

  Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath-
  pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by
  \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared
  twice with different

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

[Touch-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 Ubuntu
Touch seeded 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

[Touch-packages] [Bug 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)

2017-12-12 Thread WinEunuchs2Unix

Brand new install 16.04.3 on Skylake w/UEFI. Originally /EFI partition
was being checked so set it to 0 in /etc/fstab. But /dev/nvme0n1p5 kept
being checked no matter how long interval set using tune2fs. Finally
used grub's `fastboot` kernel command line to make "clean" message go
away.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1504688

Title:
  fsck runs on every boot (clean install, single ext4 filesystem)

Status in upstart package in Ubuntu:
  Invalid

Bug description:
  fsck runs early on *every* boot (and always says "/dev/sda1: clean ...")
  The system was always shut down using the regular Unity mechanism (Gear->Shut 
Down...)

  Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1"
  shows the date of installation and never changes.

  This system is a brand new, clean install from the 15.10 beta2 iso, with 
subsequent updates.
  I took all the installer defaults, which created a single ext4 file system.

  Please see attached:
bootscreen.png - screen shot of fsck output at start of bootup (from VM 
window)
dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: upstart 1.13.2-0ubuntu16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:10:05 2015
  InstallationDate: Installed on 2015-10-07 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemJobs:
   Error: command ['initctl', '--system', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist

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

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

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

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

[Touch-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 Ubuntu
Touch seeded 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

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

[Touch-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 Ubuntu
Touch seeded 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

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

[Touch-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 Ubuntu
Touch seeded 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:

[Touch-packages] [Bug 1475094] Re: Warning because an already existing user is tried to be created

2016-09-29 Thread WinEunuchs2Unix

Noticed this error for the first time today running `sudo apt upgrade`.
Also for the first time (single user account laptop) had to sign on to
console (ctrl+alt+F1) and (ctrl+alt+f2) because Ubuntu 16.04 login
screen wasn't working due to activating Nvidia 367.44 driver in
`Additional Drivers` screen.

Signing into console was necessary for the first time ever in order to
restore Intel integrated graphics and using the system normally.

(Kernel version 4.7.5)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launchpad.net/bugs/1475094

Title:
  Warning because an already existing user is tried to be created

Status in adduser package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in adduser package in Debian:
  New

Bug description:
  I'm using Ubuntu 15.10 dev with systemd/udev 222-1ubuntu4 and on the
  last upgrades I have noticed that these packages are trying to create
  users which already exists. On reinstalling them udev shows on setting
  up "addgroup: The group `input' already exists as a system group.
  Exiting." and systemd shows on setting up "addgroup: The group
  `systemd-journal' already exists as a system group. Exiting." and
  "addgroup: The group `systemd-journal-remote' already exists as a
  system group. Exiting.". Maybe it could be checked if a user exists to
  avoid showing a warning.

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

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

Re: [Touch-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 Ubuntu
Touch seeded 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

Re: [Touch-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 Ubuntu
Touch seeded 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

Re: [Touch-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 Ubuntu
Touch seeded 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]:

[Touch-packages] [Bug 1226472] Re: update-initramfs -u hangs; update-initramfs -u -v works

2014-11-11 Thread WinEunuchs2Unix

This happens when updating initramfs under 3.18.0-rc3 and -rc4.  Can't
remember rc1 and rc2 in detail.

Specifically 4 warning messages causes initrd to not be created (and
then you can't boot) when verbose is turned off:

[code]
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module 
r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module 
r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module 
r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module 
r8169
[/ccode]

appending the -v or -vv parameter to update-initramfs command line
allows the initrd.img to be created.  Testing it is another issue of
course.

Changes from plain-vanilla include use of dkms for EnhanceIO modules
(used for HDD caching to 32gb mSATA SSD) which are coded into /usr/share
/initramfs-tools/scripts/local-top in a script file.

update-initramfs runs normally under 3.17.1 and 3.16.6 kernels without
the -v parameter.

HTH

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1226472

Title:
  update-initramfs -u hangs; update-initramfs -u -v works

Status in “initramfs-tools” package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  For reasons totally unknown to me, `update-initramfs` (Version:
  0.103ubuntu0.2) fails to update my kernel and just hangs indefinitely
  with [sudo] `update-initramfs -u`. However, `update-initramfs -u -v`
  completes successfully:

  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-3.5.0-40-generic
  ^C
  $ sudo update-initramfs -u -v
  Available versions:  3.5.0-40-generic 3.5.0-17-generic
  Keeping /boot/initrd.img-3.5.0-40-generic.dpkg-bak
  update-initramfs: Generating /boot/initrd.img-3.5.0-40-generic
  /usr/share/initramfs-tools/hooks/framebuffer~ ignored: not alphanumeric or 
'_' file
  Adding module /lib/modules/3.5.0-40-generic/kernel/drivers/ata/libahci.ko
  Adding module /lib/modules/3.5.0-40-generic/kernel/drivers/ata/ahci.ko
  Adding module 
/lib/modules/3.5.0-40-generic/kernel/drivers/mmc/card/mmc_block.ko
  Adding binary /etc/initramfs-tools/conf.d/resume
  Adding binary /usr/lib/initramfs-tools/bin/wait-for-root
  Adding library /lib/x86_64-linux-gnu/libudev.so.0
  Adding library /lib/x86_64-linux-gnu/libc.so.6
  Adding library /lib/x86_64-linux-gnu/librt.so.1
  Adding library /lib64/ld-linux-x86-64.so.2
  Adding library /lib/x86_64-linux-gnu/libpthread.so.0
  Adding binary /sbin/modprobe
  Adding binary /sbin/rmmod
  Adding binary /sbin/blkid
  Adding library /lib/x86_64-linux-gnu/libblkid.so.1
  Adding library /lib/x86_64-linux-gnu/libuuid.so.1
  tsort: -: input contains an odd number of tokens
  Building cpio /boot/initrd.img-3.5.0-40-generic.new initramfs
  Removing current backup /boot/initrd.img-3.5.0-40-generic.dpkg-bak
  $

  I'm using Linux Mint (14), an Ubuntu fork, and I obviously expect the
  tool to work when it is not being verbose as well!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1226472/+subscriptions

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

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

[Touch-packages] [Bug 257135] Re: notify-send(1) can't replace an existing notification

[Touch-packages] [Bug 257135] Re: notify-send(1) can't replace an existing notification

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

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

[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors

[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors

[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

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

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

[Touch-packages] [Bug 706565] Re: configs with dots in file name not working in /etc/cron.d

Re: [Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted

[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed

[Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

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

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

[Touch-packages] [Bug 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)

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

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

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

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

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

[Touch-packages] [Bug 1475094] Re: Warning because an already existing user is tried to be created

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

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

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

[Touch-packages] [Bug 1226472] Re: update-initramfs -u hangs; update-initramfs -u -v works

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

29 matches

Site Navigation

Mail list logo

Footer information