[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

[WinEunuchs2Unix]

Oops I only posted bash comments and not bash code. Here is full
function:

xreset () {

# Reset xrandr to normal, first use: xrandr | grep " connected "
# HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
1107mm x 623mm
# eDP-1-1 connected primary 1920x1080+3840+2160 (normal left inverted right 
x axis y axis) 382mm x 215mm
# DP-1-1 connected 3840x2160+1920+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
xrandr --output HDMI-0  --mode 1920x1080 --pos 0x0   --rotate normal \
   --fb 1920x1080   --panning 1920x1080 \
   --output DP-1-1  --mode 3840x2160 --pos 1920x0--rotate normal \
   --output eDP-1-1 --mode 1920x1080 --pos 3840x2160 --rotate normal \
   --primary

# --panning option added because HDMI-0 was mirroring all other monitors
# and "panning" back and forth. --fb option added next day.

} # xreset

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295267

Title:
  Windows change Monitor/Desktop after screen lock

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

[WinEunuchs2Unix]

I have one TV on HDMI, one TV on Thunderboolt III and a skylake laptop
display. Every six weeks or so they will go haywire after resume. I run
this function though to fix it:

```
$ grep xreset -A5 ~/.bashrc
xreset () {

# Reset xrandr to normal, first use: xrandr | grep " connected "
# HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
1107mm x 623mm
# eDP-1-1 connected primary 1920x1080+3840+2160 (normal left inverted right 
x axis y axis) 382mm x 215mm
# DP-1-1 connected 3840x2160+1920+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
--
} # xreset
```

If it happened more frequently I would assign the function to a hot key
like CTRL+SHIFT+ALT+S or something like that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295267

Title:
  Windows change Monitor/Desktop after screen lock

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825636] Re: Battery drain during sleep. System suspended before kernel suspends all tasks

[WinEunuchs2Unix]

Reply to #22 (Timo Jyrinki):

I don't see why `tlp` is being singled out (although I do have it
installed since reporting the bug in Ask Ubuntu). I would think the
fault is more with `systemd` or perhaps Linux Kernel not understanding
how ACPI works properly. (Wild hunch). That said the results of my test
you requested:

$ cat /sys/power/mem_sleep
s2idle [deep]

I'm just hoping someone at Canonical or Linux Kernel Team has a laptop
and can confirm if their logs match the rest of ours. If they do then
dig deeper. If their logs are fine then question the users here on how
their platforms are different.

At least that's what I would do if I worked for Canonical or Linux
Kernel Team and had access to a laptop. I've read before laptops are
extremely rare in the Linux world.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825636

Title:
  Battery drain during sleep. System suspended before kernel suspends
  all tasks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1444880] Re: xrandr report inverted gamma values

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1444880

Title:
  xrandr report inverted gamma values

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690502] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160930/dswload-210)

[WinEunuchs2Unix]

Approaching the end of year 2019 and these bugs are still here. To make
matters worse users with crashing systems unrelated to these bugs are
falsely assuming they are the cause of the crash. When looking in
journalctl boot startup these are the first errors you see in RED
letters:

Nov 12 06:01:25 alien kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace 
lookup failure, AE_NOT_FOUND (20170728/dswload-210)
Nov 12 06:01:25 alien kernel: ACPI Exception: AE_NOT_FOUND, During name 
lookup/catalog (20170728/psobject-252)
Nov 12 06:01:25 alien kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp10) 
while loading table (20170728/tbxfload-228)
Nov 12 06:01:25 alien kernel: ACPI Error: 1 table load failures, 9 successful 
(20170728/tbxfload-246)

If systemd team came up with a solution to remove these 4 error messages
from journalctl that could be a quick fix / band-aid solution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690502

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20160930/dswload-210)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

[WinEunuchs2Unix]

For some this problem is answered by: [Windows option just reloads grub
bootloader after updating to Ubuntu
19.10](https://askubuntu.com/questions/1183528/windows-option-just-
reloads-grub-bootloader-after-updating-to-ubuntu-19-10/1183623#1183623).

Before following steps in answer use `boot-repair` to get diagnosis to
ensure same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845289

Title:
  Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442050

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1486445] Re: Lots of zeitgeist errors

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486445

Title:
  Lots of zeitgeist errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1486445] Re: Lots of zeitgeist errors

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486445

Title:
  Lots of zeitgeist errors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

I have three screens:

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

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

The two 1920x1080 screens wallpaper is all white.

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

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1781924] Re: Kernel wrong temperature reporting

[WinEunuchs2Unix]

This bug has been reported a few times in Ask Ubuntu. Just today (July
3rd, 2019) I was going back through `dmesg` and by chance I noticed on
June 22nd, 2019 the errors appear about a dozen times.

I've been on the same kernel version 4.14.114 LTS for a couple/few
months now but I did flirt with version 4.14.120 LTS briefly and it is
possible I was using that kernel version that day. I would have to check
journalctl to find out for sure if someone deems it relevant.

I don't view this bogus throttling error as a problem more of a
curiosity if anything.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781924

Title:
  Kernel wrong temperature reporting

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[WinEunuchs2Unix]

I've been using NVMe M.2 Samsung Pro 960 for 18 months and never had a problem.
Ubuntu 16.04.6 LTS, Kernel 4.14.114 LTS, Skylake 6700HQ, nVidia 970m
UEFI, GPT, AHCI (Intel Raid off), Secure Boot off

`/etc/fstab`:

UUID=b40b3925-70ef-447f-923e-1b05467c00e7 /   ext4
errors=remount-ro 0   1
UUID=D656-F2A8  /boot/efi   vfatumask=0077  0   1
UUID=b4512bc6-0ec8-4b17-9edd-88db0f031332 noneswapsw
0   0

`/etc/default/grub`:
GRUB_CMDLINE_LINUX_DEFAULT="noplymouth fastboot acpiphp.disable=1 
pcie_aspm=force vt.handoff=7 i915.fastboot=1 nopti nospectre_v2 nospec"

I've never had a single fsck error ever. Granted the `grub` boot option
`fastboot` means `fsck` is not run on boot but I can check once FS is
mounted RW with:

$ sudo fsck -n /dev/nvme0n1p6
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
Warning!  /dev/nvme0n1p6 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
New_Ubuntu_16.04: clean, 712096/2953920 files, 5733245/11829504 blocks

Assuming your `/etc/fstab` is the same, the two important `grub` boot
parameters are: `acpiphp.disable=1 pcie_aspm=force`. If memory serves me
correct though these were setup for suspend/resume reasons though.

I hope this helps those effected by bug a little but more importantly
that people realize the vast majority of NVMe installations work fine in
Linux.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340

Title:
  Samsung SSD corruption (fsck needed)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753884] Re: session logout after suspend

[WinEunuchs2Unix]

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

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

Method:

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

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

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

Title:
   session logout after suspend

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825636] Re: Battery drain during sleep. System suspended before kernel suspends all tasks

[WinEunuchs2Unix]

Same problem has existed for years on Ubuntu 16.04 with systemd and TLP
in use. pm-utils is installed by default but for the most part inactive
(last log entry Oct 28 2018).

OP already reported this Ask Ubuntu Q link posted 2 1/2 years ago:
- 
https://askubuntu.com/questions/828486/kernel-suspends-too-quickly-upon-resume-continues-suspend-tasks

(The answer receiving bounty award does not work and has not been
accepted!)

==

An ACPI linked question of the same "suspend to RAM too quickly" issue can be 
found here:
- 
https://unix.stackexchange.com/questions/502235/system-fails-to-suspend-acpi-ec-interrupt-blocked

There is an old ACPI bug report which I understand is because
Manufacturers hacked the specs to please Microsoft and Linux doesn't
work well during boot up. I don't think ACPI is related but just in case
here is a refresher on the error messages during boot:

ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND 
(20170728/dswload-210)
Apr 04 21:05:29 alien kernel: ACPI Exception: AE_NOT_FOUND, During name 
lookup/catalog (20170728/psobject-252)
Apr 04 21:05:29 alien kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp10) 
while loading table (20170728/tbxfload-228)
Apr 04 21:05:29 alien kernel: ACPI Error: 1 table load failures, 9 successful 
(20170728/tbxfload-246)



My log is similar to OP except that systemd shows it's fingerprints in
the suspend/freeze process:

Apr 20 01:42:39 alien systemd-sleep[32388]: 
/lib/systemd/system-sleep/r8169-reset failed wit
Apr 20 01:42:39 alien systemd-sleep[32387]: Suspending system...
-- Subject: System sleep state suspend entered
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The system has now entered the suspend sleep state.
Apr 20 01:42:39 alien kernel: PM: suspend entry (deep)
Apr 20 01:42:39 alien kernel: PM: Syncing filesystems ... done.
Apr 20 08:57:10 alien kernel: Freezing user space processes ... (elapsed 0.016 
seconds) done
Apr 20 08:57:10 alien kernel: OOM killer disabled.
Apr 20 08:57:10 alien kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds)
Apr 20 08:57:10 alien kernel: Suspending console(s) (use no_console_suspend to 
debug)
Apr 20 08:57:10 alien kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Apr 20 08:57:10 alien kernel: sd 1:0:0:0: [sda] Stopping disk
Apr 20 08:57:10 alien kernel: ACPI: EC: interrupt blocked
Apr 20 08:57:10 alien kernel: ACPI: Preparing to enter system sleep state S3
Apr 20 08:57:10 alien kernel: ACPI: EC: event blocked
Apr 20 08:57:10 alien kernel: ACPI: EC: EC stopped
Apr 20 08:57:10 alien kernel: PM: Saving platform NVS memory
Apr 20 08:57:10 alien kernel: Disabling non-boot CPUs ...
Apr 20 08:57:10 alien kernel: smpboot: CPU 1 is now offline
Apr 20 08:57:10 alien kernel: smpboot: CPU 2 is now offline
Apr 20 08:57:10 alien kernel: smpboot: CPU 3 is now offline
Apr 20 08:57:10 alien kernel: smpboot: CPU 4 is now offline
Apr 20 08:57:10 alien kernel: smpboot: CPU 5 is now offline
Apr 20 08:57:10 alien kernel: smpboot: CPU 6 is now offline
Apr 20 08:57:10 alien kernel: smpboot: CPU 7 is now offline
Apr 20 08:57:10 alien kernel: ACPI: Low-level resume complete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825636

Title:
  Battery drain during sleep. System suspended before kernel suspends
  all tasks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1825636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1473142] Re: sh: 1: /lib/libc.so.6: not found

[WinEunuchs2Unix]

Doesn't appear to be a big deal other than Battery information doesn't
appear but, this error still occurs in Ubuntu 16.04.5 LTS when calling
`hardinfo` from the command line:

$ hardinfo
sh: 1: /lib/libc.so.6: not found
sh: 1: gnome-about: not found
sh: 0: -c requires an argument
sh: 0: -c requires an argument
sh: 0: -c requires an argument

< Last line repeats many times >

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473142

Title:
  sh: 1: /lib/libc.so.6: not found

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

[WinEunuchs2Unix]

@Ole and @Feng.

The normal methodology of `echo XHC > /proc/acpi/wakeup` had no effect
whether `enabled` or `disabled`. By default `enabled` and all others are
`disabled`.

I also have `tlp` defaults which is probably USB_AUTOSUSPEND.

I could go into console mode and type `pm_suspend` (it's set to deep /
mem, if you set it to freeze all heck breaks loose). At this point I can
see 5 or 6 repetitions of three line groups stating "USB 1-1, Port 2
does it have a bad cable?"

Indeed there could be a cheap dollar store cable or Y cable from China
with data / power only that went flaky on me.

With the script I posted everything works reliably now although I
suspect Resume takes a couple of seconds longer than necessary as I see
`journalctl` spammed with every single USB device being unbound (powered
off) and rebound (powered on).

I've only tested with `4.14.78` so far because life is busy with other
things...

I'll try to keep you posted and try other options that you've mentioned
and report back. Thank you for taking the time to float new ideas.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774994

Title:
  Laptop wakes up immediately after suspend or hibernation

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

[WinEunuchs2Unix]

@@Kai-Heng Feng (kaihengfeng) Everything seems to be fixed for both this
old bug and for new problems I was having over last few days.

I found a bug report from 2010 (link in script below) and used this:

#!/bin/bash

# Original script was using /bin/sh but shellcheck reporting warnings.

# NAME: custom-xhci_hcd
# PATH: /lib/systemd/system-sleep
# CALL: Called from SystemD automatically
# DESC: Suspend broken for USB3.0 as of Oct 25/2018 various kernels all at once

# DATE: Oct 28 2018.

# NOTE: From comment #61 at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/522998

TMPLIST=/tmp/xhci-dev-list

# Original script was: case "${1}" in hibernate|suspend)

case $1/$2 in
  pre/*)
echo "$0: Going to $2..."
echo -n '' > $TMPLIST
  for i in `ls /sys/bus/pci/drivers/xhci_hcd/ | egrep 
'[0-9a-z]+\:[0-9a-z]+\:.*$'`; do
  # Unbind xhci_hcd for first device :XX:XX.X:
   echo -n "$i" | tee /sys/bus/pci/drivers/xhci_hcd/unbind
   echo "$i" >> $TMPLIST
  done
;;
  post/*)
echo "$0: Waking up from $2..."
for i in `cat $TMPLIST`; do
  # Bind xhci_hcd for first device :XX:XX.X:
  echo -n "$i" | tee /sys/bus/pci/drivers/xhci_hcd/bind
done
rm $TMPLIST
;;
esac

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774994

Title:
  Laptop wakes up immediately after suspend or hibernation

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

[WinEunuchs2Unix]

@Kai-Heng Feng (kaihengfeng) just an update...

Suddenly my suspend totally broke down (wakes immediately from suspend)
using same kernel I had for a few months (outdated `4.13.0-36-generic`).

In order to update to newer kernels I had to install libssl1.1 to side-
step linux-header installation errors.

Either libsl1.1 or newer kernels broke dkms makefile's for nvidia,
bbswitch, virtual box, etc. So I had to use: `sudo apt install libelf-
dev`

I ended up successfully upgrading to mainline kernel `4.14.78` but now
suspend takes 30 seconds to break and goes to login screen instead.

So I'm out of the frying pan and into the fire...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774994

Title:
  Laptop wakes up immediately after suspend or hibernation

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

[WinEunuchs2Unix]

Hi
Kai-Heng Feng,

I presume you want me to try the 9 rc's in the `4.15` kernel chain? I
assume the 8 to 9 rc's in `4.13`, 4.14`, `4.16`, `4.17`, `4.18` and `4.19`
rc's don't have to be installed?

Also would it make sense to try the LTS kernel `4.14.78` first and see if
it's already been fixed? Then crawl backwards through that chain to see
when it was last broken? Another reason is `4.14` LTS kernels I would
actually keep around where as the `rc` kernels I have to delete. Also `apt
remove` has been broken for some kernels with bad symbolic links requiring
editing the bash script `postinst` (or something like that) to force
removal of unwanted kernels.

Thank you for showing interest in this closed bug report.

On Wed, Oct 17, 2018 at 10:00 PM Kai-Heng Feng 
wrote:

> Would it be possible for you to do a kernel bisection?
>
> First, find the last good -rc kernel and the first bad -rc kernel from
> http://kernel.ubuntu.com/~kernel-ppa/mainline/
>
> Then,
> $ sudo apt build-dep linux
> $ git clone git://
> git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> $ cd linux
> $ git bisect start
> $ git bisect good $(the good version you found)
> $ git bisect bad $(the bad version found)
> $ make localmodconfig
> $ make -j`nproc` deb-pkg
> Install the newly built kernel, then reboot with it.
> If the issue still happens,
> $ git bisect bad
> Otherwise,
> $ git bisect good
> Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes
> the regression.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774994
>
> Title:
>   Laptop wakes up immediately after suspend or hibernation
>
> Status in linux package in Ubuntu:
>   Expired
>
> Bug description:
>   After going into suspend (via command line or lid close), the MacBook
>   Pro (early 2015) wakes up immediately again. Same for hibernation.
>   Running Ubuntu 18.04.
>
>   extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open
>   cycle:
>
>   [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013)
> (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16
> 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
>   [ ... ]
>   [  778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip
> table err:-23
>   [  783.011399] PM: suspend entry (deep)
>   [  783.011400] PM: Syncing filesystems ... done.
>   [  783.028538] Freezing user space processes ... (elapsed 0.002 seconds)
> done.
>   [  783.030844] OOM killer disabled.
>   [  783.030844] Freezing remaining freezable tasks ... (elapsed 0.001
> seconds) done.
>   [  783.032193] Suspending console(s) (use no_console_suspend to debug)
>   [  783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache
>   [  783.054107] sd 1:0:0:0: [sda] Stopping disk
>   [  783.146124] thunderbolt :07:00.0: suspending...
>   [  783.146685] thunderbolt :07:00.0: suspend finished
>   [  783.146689] thunderbolt :07:00.0: stopping RX ring 0
>   [  783.146698] thunderbolt :07:00.0: disabling interrupt at register
> 0x38200 bit 12 (0x1001 -> 0x1)
>   [  783.146710] thunderbolt :07:00.0: stopping TX ring 0
>   [  783.146718] thunderbolt :07:00.0: disabling interrupt at register
> 0x38200 bit 0 (0x1 -> 0x0)
>   [  783.146725] thunderbolt :07:00.0: control channel stopped
>   [  783.246464] ACPI: Preparing to enter system sleep state S3
>   [  783.418015] ACPI: EC: event blocked
>   [  783.418016] ACPI: EC: EC stopped
>   [  783.418018] PM: Saving platform NVS memory
>   [  783.418027] Disabling non-boot CPUs ...
>   [  783.434574] IRQ 65: no longer affine to CPU1
>   [  783.435629] smpboot: CPU 1 is now offline
>   [  783.454574] IRQ 66: no longer affine to CPU2
>   [  783.456378] smpboot: CPU 2 is now offline
>   [  783.478405] IRQ 21: no longer affine to CPU3
>   [  783.478414] IRQ 43: no longer affine to CPU3
>   [  783.478435] IRQ 71: no longer affine to CPU3
>   [  783.479449] smpboot: CPU 3 is now offline
>   [  783.481656] ACPI: Low-level resume complete
>   [  783.481733] ACPI: EC: EC started
>   [  783.481734] PM: Restoring platform NVS memory
>   [  783.482160] Enabling non-boot CPUs ...
>   [  783.482240] x86: Booting SMP configuration:
>   [  783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2
>   [  783.558589]  cache: parent cpu1 should not be sleeping
>   [  783.687159] CPU1 is up
>   [  783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1
>   [  783.687812]  cache: parent cpu2 should not be sleeping
>   [  783.688001] CPU2 is up
>   [  783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3
>   [  783.783709]  cache: parent cpu3 should not be sleeping
>   [  783.978233] CPU3 is up
>   [  783.982020] ACPI: Waking up from system sleep state S3
>   [  784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to
> reestablish PCI tunnels...
>   [  784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to
> reestablish PCI 

[Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

[WinEunuchs2Unix]

It's a kernel issue.

Using Ubuntu 16.04.5 LTS with the 18.04.1 LTS's kernel `4.15.0-36` when
you try to suspend it resumes after a dozen seconds or so. If you use
kernel `4.13.0-36` the suspend/resume cycle is normal. I believe
`4.13.0-36` was released for Ubuntu 17.10 which I've never installed and
it is EOL but it works best for my AW17R3 Laptop so I'll keep using it
until something newer comes along that works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774994

Title:
  Laptop wakes up immediately after suspend or hibernation

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579580

Title:
  ureadahead reports relative path errors in journalctl output

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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 

[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock

[WinEunuchs2Unix]

Comment #86 should be deleted because the Windows fluff is detracting
from serious Linux conversation.

I often close the Intel HD530 driven laptop lid and windows there move
to nVidia GTX 970M HDMI hardwired external TV. The windows on the
Thunderbolt Intel HD 530 driven external monitor TV stay consistent.

If I do not turn on the TV's before resuming from suspend, then the
windows on the Thunderbolt driven TV (right side) disappear off screen
and I have to use + to select the disappeared window. Then I
need to hold ++ and move mouse left to force window
back onto canvass.

Another annoying non-Ubuntu-fault-probably-Xorg-fault problem is that
when opening and closing laptop lid both external TVs reset. The Intel
HD 530 Thunderbolt connected via DP to HDMI converter plug resets it's
XRANDR setting for --gamma 1:.9:.7 --brightness .5 so I have to recall
it from bash history and resend the command.

When one monitor deactivates, cannot the windows simply move to the
other screens (as they do now) without reseting the other monitors/TVs?

In /var/log/Xorg.log nVidia sends out messages but Intel HD 530 (i915
driver) doesn't appear to send out messages.

Unfortunately googling how to override these issues via XORG hooks or
even a custom script that monitors UDEV events sheds no light on the
situation.

Overall things have improved greatly over the last three years (18.04
problems excluded) so I don't want to sound negative. Laptop eDP Windows
do move properly to main HDMI TV on lid close and back to laptop eDP on
lid open.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295267

Title:
  Windows change Monitor/Desktop after screen lock

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation

[WinEunuchs2Unix]

I've experienced similar situations for years where when resuming from
suspend, the system immediately completes uncompleted sleep and then
wakes up. More of an annoyance and loss of a second or two of life than
anything else.

Today however the cycle has changed with advent of nVidia drivers. Now
like OP system resumes when going to sleep. Key points from OP log are:

[ 783.011399] PM: suspend entry (deep)
[ 783.011400] PM: Syncing filesystems ... done.
[ 783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done.

[ 783.479449] smpboot: CPU 3 is now offline
[ 783.481656] ACPI: Low-level resume complete
[ 783.481733] ACPI: EC: EC started
[ 783.481734] PM: Restoring platform NVS memory
[ 783.482160] Enabling non-boot CPUs ...
[ 783.482240] x86: Booting SMP configuration:
[ 783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 783.558589] cache: parent cpu1 should not be sleeping
[ 783.687159] CPU1 is up

OP's log cuts off too early. Adding information from my own log today:

Aug 06 17:27:02 alien kernel: CPU7 is up
Aug 06 17:27:02 alien kernel: ACPI: Waking up from system sleep state S3
Aug 06 17:27:02 alien kernel: ACPI: EC: interrupt unblocked
Aug 06 17:27:02 alien kernel: ACPI: EC: event unblocked
Aug 06 17:27:02 alien kernel: usb usb3: root hub lost power or was reset
Aug 06 17:27:02 alien kernel: usb usb4: root hub lost power or was reset
Aug 06 17:27:02 alien kernel: sd 1:0:0:0: [sda] Starting disk

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774994

Title:
  Laptop wakes up immediately after suspend or hibernation

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377653

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587154

Title:
  --working-directory does not work anymore

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759462

Title:
  Keyboard shortcuts not operational on 18.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

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

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

Signed in with Unity under Xorg.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759462

Title:
  Keyboard shortcuts not operational on 18.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766851] Re: Missing `linux-update-symlinks` causes Linux package installation to fail

[WinEunuchs2Unix]

Same problem with Kernel 4.14.36: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.14.36/

Also I would suspect (but cannot confirm) that Kernel 4.16.4 will suffer
the same fate.

For the first time all three of these kernels (including OP's 4.17-rc2)
deviated from history where there were three `.deb` files: headers-all,
headers, linux-image (aka image_unsigned). A fourth `.deb` was
introduced called: ` linux-
modules-4.14.36-041436-generic_4.14.36-041436.201804240906_amd64.deb`

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766851

Title:
  Missing `linux-update-symlinks` causes Linux package installation to
  fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766851/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706565

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[WinEunuchs2Unix]

@Robert Focht `4.11.5` is fairly old and won't have Meltdown or Spectre
fixes. Do you mean `4.15.5`? Regardless see this link to get Skylake
through Kabylake drivers: https://askubuntu.com/questions/832524
/updated-kernel-to-4-8-now-missing-firmware-warnings

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611124

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611945

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

Message:

bus: MMIO read of  FAULT at 022554 [ IBUS ]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1684123

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

[WinEunuchs2Unix]

@dmytriy--I suspect your suspend/resume problems are unrelated simply
because there are hundreds of different problems in that area. I suggest
searching Ask Ubuntu or Linux & Unix sites. For example, my Alienware
AW17R3 with i-7 6700HQ (Skylake) wouldn't suspend/resume because of NVMe
M.2 Gen 3.0 x 4 SSD. The solution, for me and a few others, was to put a
kernel command line parameter in /etc/default/grub.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584407

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20150930/dswload-210)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568560

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611945

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

[WinEunuchs2Unix]

#15 says problem went away but is on Kernel 4.4 and Kerne 4.8 where
message was "hacked" to not display. With kernels 4.9, 4.10, etc. the
message reappears as per bug report here:
https://bugzilla.kernel.org/show_bug.cgi?id=193531

#17 closing this bug based upon #15 should be reconsidered.

Also note this bug is a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690502 which has
fewer subscribers but more accurate information.

There is a third duplicate bug report in launchpad which I don't have
the link for just now.

** Bug watch added: Linux Kernel Bug Tracker #193531
   https://bugzilla.kernel.org/show_bug.cgi?id=193531

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584407

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20150930/dswload-210)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309535

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690502] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160930/dswload-210)

[WinEunuchs2Unix]

Same bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407 opened one
year earlier.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690502

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20160930/dswload-210)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1680268] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

[WinEunuchs2Unix]

Same bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690502

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680268

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20150930/dswload-210)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

[WinEunuchs2Unix]

Error remains Dell based Skylake 6700HQ, HM170, nVidia 384.98, NVMe
Gen3x4 M.2 SSD, Ubuntu 16.04.3, Kernel 4.14.4:

Dec 12 19:08:16 alien kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace 
lookup failure, AE_NOT_FOUND (20170728/dswload-210)
Dec 12 19:08:16 alien kernel: ACPI Exception: AE_NOT_FOUND, During name 
lookup/catalog (20170728/psobject-252)
Dec 12 19:08:16 alien kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp10) 
while loading table (20170728/tbxfload-228)
Dec 12 19:08:16 alien kernel: ACPI Error: 1 table load failures, 9 successful 
(20170728/tbxfload-246)
Dec

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584407

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20150930/dswload-210)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504688

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[WinEunuchs2Unix]

Kai-Heng sorry I can't try it right away. I'm still struggling with
systemd's kexec-load@service to quicken reboot times as I struggle with
nVidia having HDMI sound turned off by default BIOS POST. In the
meantime I've blacklisted `ath10k_pci` and that appears to have saved
2-3 seconds off the boot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520343

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1520343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[WinEunuchs2Unix]

Kai-Heng,

I was on Hardware stack for awhile but had problems with. Remember many
users opt out of HWE even though it's the default.

I was running 4.14.2 mainline but `kexec` was broken after 4.12 so I
dropped into 4.4.0-101 provided by Ubuntu to make `kexec` work properly.

I do have Ubuntu kernels 4.10.0-28, 4.10.0-37...-38 and -40 but I have
to analyze the release dates to figure out which real Linux kernel
version they are equivalent to.

Are you suggesting an HWE version off the 4.10 kernel tree fixes the
problem and solution in comment #22 is no longer needed???

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520343

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1520343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[WinEunuchs2Unix]

Two years later and bug still lurking on this new (to me) laptop. Ubuntu
16.04, Kernel 4.4.0-101-generic, Skylake HM170, nVidia GTX970M, HD530
graphics, USB-C Thunderbolt3, NVMe M.2 Samsung Pro 960 SSD, etc.

3c:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac
Wireless Network Adapter [168c:003e] (rev 32), dmesg:

[3.784502] ath10k_pci :3c:00.0: enabling device ( -> 0002)
[3.787048] ath10k_pci :3c:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
[4.019658] ath10k_pci :3c:00.0: Direct firmware load for 
ath10k/cal-pci-:3c:00.0.bin failed with error -2
[4.019903] ath10k_pci :3c:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[4.019905] ath10k_pci :3c:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[6.202327] ath10k_pci :3c:00.0: qca6174 hw3.2 (0x0503, 0x00340aff 
sub 1a56:1535) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4 bdapi 2 htt-ver 3.26 
wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features 
wowlan,ignore-otp,no-4addr-pad
[6.202330] ath10k_pci :3c:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
[6.269850] ath: EEPROM regdomain: 0x69
[6.269852] ath: EEPROM indicates we should expect a direct regpair map
[6.269853] ath: Country alpha2 being used: 00
[6.269854] ath: Regpair used: 0x69
[6.273854] ath10k_pci :3c:00.0 wlp60s0: renamed from wlan0
[   29.191292] ath: EEPROM regdomain: 0x807c
[   29.191294] ath: EEPROM indicates we should expect a country code
[   29.191295] ath: doing EEPROM country->regdmn map search
[   29.191295] ath: country maps to regdmn code: 0x3a
[   29.191296] ath: Country alpha2 being used: CA
[   29.191297] ath: Regpair used: 0x3a
[   29.191298] ath: regdomain 0x807c dynamically updated by country IE

I use the built-in Ethernet and not the built-in WiFi so not a big deal
today. But would still like to see it fixed some day. I intentionally
bought a brand new laptop first released two years ago so it wouldn't
have bleeding-edge bugs :(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520343

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1520343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1713940] Re: kexec-tools 2.0.14 fails to load 4.12+ crash kernels

[WinEunuchs2Unix]

Same error Ubuntu 16.04.3 LTS, kexec-tools apt-installed today, Kernel
4.12.2, Skylake HM170, nVidia GTX 970M, NVMe M.2 Gen 3x4 SSD:

$ sudo kexec -l /boot/vmlinuz-`uname -r` --initrd=/boot/initrd.img-`uname -r` 
--reuse-cmdline
Unknown type (Reserved) while parsing /sys/firmware/memmap/15/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/5/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/23/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/3/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/21/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/1/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/18/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/8/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Unknown E820 type) while parsing /sys/firmware/memmap/16/type. 
Please report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/22/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/12/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/20/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/10/type. Please 
report this as bug. Using RANGE_RESERVED now.
Unknown type (Reserved) while parsing /sys/firmware/memmap/19/type. Please 
report this as bug. Using RANGE_RESERVED now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713940

Title:
  kexec-tools 2.0.14 fails to load 4.12+ crash kernels

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655100] Re: NVME devices and Network devices disappears upon suspend

[WinEunuchs2Unix]

Confirm this bug occurs on Ubuntu 16.04 w/Alienware 17R3, i7 6700HQ,
HM170 chipset. The workaround to use `acpiphp.disable=1` on kernel
command line fixes suspend/resume cycle.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655100

Title:
  NVME devices and Network devices disappears upon suspend

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

>From /var/log/syslog today:

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1369216

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377653

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377653

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377653

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377653

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to 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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1575484] Re: "Set document metadata failed"

[WinEunuchs2Unix]

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

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

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

Title:
  "Set document metadata failed"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1589028] Re: Improper blocksize set by usb-creator, leads to problems during formatting

[WinEunuchs2Unix]

Simply use `dd` to write out 512 bytes (bc=1) of zeros (if=/dev/null) to
your usb drive (of=dev/sdX) where X=the drive letter ***BE VERY CAREFUL
'X' IS RIGHT LETTER*** then you can reformat it using `gparted`.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589028

Title:
  Improper blocksize set by usb-creator, leads to problems during
  formatting

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

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

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1659339] Re: "libmtp error: Could not send object" when copying a file to MTP folder

[WinEunuchs2Unix]

** Also affects: ubuntu
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659339

Title:
  "libmtp error: Could not send object" when copying a file to MTP
  folder

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[WinEunuchs2Unix]

The warnings applied to Kabylake before it was even released / sold. Anyway
a few days ago the drivers were released so you can fix the error for real.
See:
http://askubuntu.com/questions/832524/updated-kernel-to-4-8-now-missing-firmware-warnings

On Sat, Feb 18, 2017 at 9:48 PM, simon  wrote:

> The smart thing to do is check and only show this message if using Kaby
> Lake processor. Why worry uses at all?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1611124
>
> Title:
>   W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
>   for module i915
>
> Status in xen:
>   Unknown
> Status in linux-firmware package in Ubuntu:
>   Invalid
>
> Bug description:
>   $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency
>
>   [...]
>
>   update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency
>   W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for
> module i915
>   W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for
> module i915
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: linux-firmware 1.159
>   Uname: Linux 4.8.0-040800rc1-lowlatency x86_64
>   ApportVersion: 2.20.3-0ubuntu5
>   Architecture: amd64
>   Date: Mon Aug  8 17:50:38 2016
>   Dependencies:
>
>   InstallationDate: Installed on 2015-07-26 (379 days ago)
>   InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64
> (20150723)
>   PackageArchitecture: all
>   SourcePackage: linux-firmware
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/xen/+bug/1611124/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611124

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915

[WinEunuchs2Unix]

To make these annoying warnings go away I used:

$ sudo cp assembly/hello  /lib/firmware/i915/kbl_dmc_ver1_01.bin
$ sudo cp assembly/hello /lib/firmware/i915/kbl_guc_ver9_14.bin
$ sudo cp assembly/hello /lib/firmware/i915/bxt_guc_ver8_7.bin
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.9.5-040905-generic

Voila! Error (warning) messages went away. It's been working fine for
1/2 hour.

"hello" is a 504 byte assembly program that simply says "Hello World!"
when run. I presume you can copy any executable program you want. When
Intel eventually gets around releasing the "kaby lake" processor and
appropriate drivers they will overwrite my fake drivers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611124

Title:
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
  for module i915

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1589028] Re: Improper blocksize set by usb-creator, leads to problems during formatting

[WinEunuchs2Unix]

Can't you use `dd if=/dev/zero of=/dev/sdX count=100` to wipe out MBR and
partition table? Then gparted will just see a new drive. Note sdX = sdb,
sdc or whatever your flash drive is.

On Fri, Jan 27, 2017 at 4:55 AM, EoflaOE <1589...@bugs.launchpad.net>
wrote:

> I did it on Ubuntu Server ISO using usb-creator-gtk, using my general
> USB flash drive and its size is 8GB, and it did the same thing so I
> deleted the culprit partition using Gparted, and no errors like that is
> displayed and it removed the partition completely, then, I was able to
> create the FAT32 partition. From now on, I have to use Rufus, the
> perfect tool on Windows.
>
> usb-creator-gtk tried to set the flash drive's partition into ISO 9660,
> which means it is not recognized by some systems, and is read only. I
> removed the partition completely that is ISO 9660, then I formatted it
> on FAT32 (partition size is 7.6GB after ISO 9660 removal).
>
> So I suggest everyone who wants to create a Ubuntu flash drive must use
> Rufus, or Universal USB Creator, until this bug is fixed to avoid damage
> to your USB flash drive's partition.
>
> Some users (like me) have this bug but they are able to remove the
> culprit, iso9660 partition and recreating the FAT32, useful, read and
> write partition. Others have this bug but they are not be able to remove
> the culprit, iso9660 partition and shows that error.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1589028
>
> Title:
>   Improper blocksize set by usb-creator, leads to problems during
>   formatting
>
> Status in parted package in Ubuntu:
>   Confirmed
> Status in parted package in Debian:
>   Fix Released
>
> Bug description:
>   When ever I create a bootable USB using usb-creator , and when I try
>   to format it after my work is done, I get this error
>
>   “The Driver descriptor says physical block size is 2048 bytes, but
>   Linux says it is 512” in Gparted. (screen shot in the attachments)
>
>   Furthermore , The USB is divided into strange partitions (image
>   attached). and shows the 16GB partition as 60GB partition.
>
>   I presume that this is because of setting the blocksize to 100 by
>   this tool : as in the source code here : https://bazaar.launchpad.net
>   /~usb-creator-hackers/usb-creator/trunk/view/474/bin/usb-creator-
>   helper#L111
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: usb-creator-gtk 0.3.2
>   ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sat Jun  4 08:53:43 2016
>   InstallationDate: Installed on 2016-05-30 (4 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   SourcePackage: usb-creator
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UsbCreatorLog:
>usb-creator 2016-06-04 08:53:29,852 (DEBUG) backend.py:24:
> UDisks2Backend
>usb-creator 2016-06-04 08:53:30,152 (DEBUG) backend.py:64:
> detect_devices
>usb-creator 2016-06-04 08:53:30,157 (DEBUG) backend.py:104: drive
> added: /org/freedesktop/UDisks2/block_devices/sr0
>usb-creator 2016-06-04 08:53:30,157 (DEBUG) backend.py:118: not adding
> device: 0 byte disk.
>usb-creator 2016-06-04 08:53:32,702 (DEBUG) backend.py:181:
> cancel_install
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/parted/+bug/
> 1589028/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589028

Title:
  Improper blocksize set by usb-creator, leads to problems during
  formatting

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

Thank you for the update!

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506704

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475094

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1486450] Re: Error in loading other_hosts file

[WinEunuchs2Unix]

Same here:

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

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

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

Title:
  Error in loading other_hosts file

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

Watson the game is afoot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506704

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

On the hub are:

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506704

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506704

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

fc-cache -rv

Then log out and log back in.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506704

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550351] Re: [Asus P8Z68-V LX] suspend/resume failure

[WinEunuchs2Unix]

I'd like to delete my previous two comments because on a second Suspend
under 3.13.0-32 the laptop resumed immediately and led to a system crash
again. However I'm loath to delete what's already been written.

A few months whilst still running Windows 7 ago I changed the BIOS to
wake on USB activity for a now shelved project for the UPS triggered USB
interrupt to send out an e-mail that the power has gone off.

It turns out syslog under Ubuntu is now being spammed with the message:
 "hub 4-0:1.0: Cannot enable port 3.  Maybe the USB cable is bad?"

Turning off the BIOS option to wake up on USB fixed the problem with
immediate Resume after Suspend followed by crash in Ubuntu. I don't have
Windows 7 reinstalled yet to see if the same happens there.

My apologies to those I mislead based on one-time test results. The new
test results have proven true 3 times so far :).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550351

Title:
  [Asus P8Z68-V LX] suspend/resume failure

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550351] Re: [Asus P8Z68-V LX] suspend/resume failure

[WinEunuchs2Unix]

Christopher M. Penalver (penalvch) , Thank you for the advise. I'm
currently struggling to download a valid ISO to reinstall Win 7 smacked
by Intel RST. Using an earlier Kernel is not a big deal today. I assume
Gregg and his army of programmers will fix the Kernel within a couple of
Sundays. If future Kernels do not fix the bug then I'll file a report
with the procedures as you suggest.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550351

Title:
  [Asus P8Z68-V LX] suspend/resume failure

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550351] Re: [System manufacturer System Product Name] suspend/resume failure

[WinEunuchs2Unix]

Trusty 14.04, Kernel 3.13.0-79 on Dell Inspiron 7720 17R SE Bios version
A16, 10/20/213 also crashes.

A couple of days ago (after Ubuntu 55MB and then 38MB automatic updates)
it started immediately Resuming after Suspend.

Regressing to 3.13.0-32 fixes Suspend. Closing lid or initiating from
system menu works properly.

"cat /proc/acpi/wakeup" returns same results under both 3.13.0-32 and
3.13.0-79.

HTH

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550351

Title:
  [System manufacturer System Product Name] suspend/resume failure

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

Why is showing up in my google in box?




More

*1* of *635*


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

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

 ** Tags added: trusty

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

 Title:
   Dual screen greeter can break 3D acceleration

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

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

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

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

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

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

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


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

Title:
  Dual screen greeter can break 3D acceleration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1323089

Title:
  wpa_supplicant writes to syslog every 2 minutes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349740] Re: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

[WinEunuchs2Unix]

Same issue on stock Dell Inspiron 17R SE 7720, Ubuntu 14.04 w/EnhanceIO
ssd caching, Win 7 w/Intel iRST ssd caching, Linux 3.17.4 kernel.

An hour of googling led to kernel parameter pci=nocrs without any change
except, clearing up the message kernel: [0.211061] PCI: Ignoring
host bridge windows from ACPI; if necessary, use pci=use_crs and
report a bug

In google circles David Rientjes, Rafael J. Wysocki and Jiang Liu touch
on this issue but only a patch for ACPI CPU errors was released (as best
I can decipher).

A few bug reports were issued for kernel: [0.216171]
\_SB_.PCI0:_OSC invalid UUID this year but expired because another user
didn't confirm it.  FTR this error also exists in my /var/log/syslog.

Hopefully these annoying messages can be suppressed because whilst one
is looking for a REAL error these ones send him/her down a rabbit hole
require hours of goggling update-initramfs and reboots only to discover
a false-positive and move onto the next trial  error repair option.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349740

Title:
  acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1226472

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1336994] Re: Panning and full screen window size broken when using HDMI port

[WinEunuchs2Unix]

It turns out the bug of Full Screen automatically reverting to the built
in display rather than the active/current display was caused by FireFox
and does not occur in Chromium.  Unfortunately I noticed it with a new
laptop that had built in HDMI rather than the old laptop which had VGA
and then a VGA to HDMI converter box but was NOT using FireFox.  On top
of that there was new Kernel versions, new Windows 7 with new Intel
Rapid Storage Technology, new UEFI, new OROM, etc. etc.

The resuming from suspend is NOT a factor in mitigating the bug, I had
just happened to have run Chromium rather than FireFox at that time.

I'm not suggesting Chromium is better than FireFox.  They both have
strengths and weaknesses.  For example on Linux FireFox has superior
scrolling and mouse control.  OTH Google Chrome (don't know about
Chromium) scrolls just as nicely in Windows as FireFox does in Linux.

I just retested in Kernel 3.17-rc6 and Firefox still switches to the
built-in display when you select full screen while watching tv
broadcasts in rt. com or aljazeera. com on the external TV.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336994

Title:
  Panning and full screen window size broken when using HDMI port

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1336994] Re: Panning and full screen window size broken when using HDMI port

[WinEunuchs2Unix]

Resumed from suspend this morning and loo and behold the external TV
remains in full screen mode but now the unity bar will display on the
top if you type into google or terminal on the built-in display.  On the
old laptop there used to be a problem where Fn+Fx ACPI hotkeys for
brightness would only work after suspend/resume so this issue could be
related to that old problem.

Note that this is working correctly with the External TV defined to the
right and Built-in display defined on the left which is contrary to
previous advise.  Using current version 3.17-rc5 as of Sept 18, 2014.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336994

Title:
  Panning and full screen window size broken when using HDMI port

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1318351] Re: mdadm doesn't assemble imsm raids during normal boot

[WinEunuchs2Unix]

Comment #3 was super helpful after I ran dmraid -rE and the most recent
kernel version wouldn't boot anymore.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318351

Title:
  mdadm doesn't assemble imsm raids during normal boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1336994] Re: Panning and full screen window size broken when using HDMI port

[WinEunuchs2Unix]

I'm just setting up a Dell Inspiron 7720 (17R SE) which is probably
similar to yours.  I haven't played with Nvidia drivers yet and
everything is default install.  My previous laptop was VGA out to the TV
and I thought the new problems were related to Xorg and HDMI broken vs
VGA working fine.

The bug I have is when going full screen for a video/flash player it
always goes to the built-in display instead of the external TV which I
want.  In ask Ubuntu another user with this problem got the answer to
virtually move the external display to the left and the built-in display
to the right.  I tried this and it successfully went full screen to the
external TV.

However if I type into Terminal or another window on the built-in
display the external display drops out of full screen into normalized
window size which I consider a bug of unknown origin yet.

Having to virtually assign the external TV to the left panel and the
built-in laptop display to the right panel is counter-intuitive to their
real life positions and a pain for accessing the lanucher which now has
to be activated with the super-key because the mouse just won't bump the
hidden launcher properly without falling into the TV's window.

What little I know is Intel HD4000 GPU and Nvidia 650GT GPU.  Sandy-
Bridge 3630QM quad core and mobo chipset family 77 supporting Intel
Rapid Storage Technology to accelerate HDD to SDD (once I finish
configuring dm-cache or bcache)  mdadm is up and running to mimic Intel
Raid-0 defined in OROM.  UEFI is off and MBR / dospartitions are on.

I'll falling this bug thread and see what develops.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336994

Title:
  Panning and full screen window size broken when using HDMI port

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1336994] Re: Panning and full screen window size broken when using HDMI port

[WinEunuchs2Unix]

^^^ --- Kernel versions above 3.15.10, 3.16.3 and 3.17-rc5.  Ubuntu
14.04.1.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336994

Title:
  Panning and full screen window size broken when using HDMI port

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1336994] Re: Panning and full screen window size broken when using HDMI port

[WinEunuchs2Unix]

^^^  Oops Ivy-Bridge not Sandy-Bridge.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336994

Title:
  Panning and full screen window size broken when using HDMI port

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

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

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

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

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

Title:
  Dual screen greeter can break 3D acceleration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

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

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

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

~$

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

Title:
  wpa_supplicant writes to syslog every 2 minutes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

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

Title:
  wpa_supplicant writes to syslog every 2 minutes

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

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

Title:
  Dual screen greeter can break 3D acceleration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1326161] Re: [Toshiba Satellite P70-A] Brightness Hotkey Doesn't Work

[WinEunuchs2Unix]

Christopher,

Sorry for the long delay I had put the no hotkeys on cold boot, on
suspend/resume only problem on the back-burner while I solved higher
priority problems.  I tried to file the apport bug report but my Kernel
versions (after house cleaning 8 older versions) are only 3.15.7 and
3.15.8 which are unacceptable to apport.

What kernel version would you recommend installing?  I have downloaded
the latest Unbuntu 14.04.1 to DVD but have not installed it out of
apprehension it might regress my current Kernel bug fixes which I really
enjoy.

TIA.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326161

Title:
  [Toshiba Satellite P70-A] Brightness Hotkey Doesn't Work

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1125944

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1279544] Re: lsusb different device id when using usb hub

[WinEunuchs2Unix]

I'm also having weird problems with 1a40:0101 Terminus Technology Inc.
4-Port HUB when daisy chained through 2109:0812 VIA Labs Inc. USB 3.0
- 4 port hub but I'm still in the fact gathering stage with lsbusb,
usb-devices, udevadm info, udevadm monitor, udevadm export-db, lspci,
gedit /var/log/kern.log commands and .rules files.  It's been a
fascinating 2 weeks of hobby hours consumption.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279544

Title:
  lsusb different device id when using usb hub

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[WinEunuchs2Unix]

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

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

Title:
  Displaylink slow graphic performance on Ubuntu 13

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1006676] Re: showkey fails with Couldn't get a file descriptor referring to the console

[WinEunuchs2Unix]

Permission denied would follow terse convention.  You must run as
root would be verbose convention I think.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006676

Title:
  showkey fails with Couldn't get a file descriptor referring to the
  console

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1326161] Re: [Toshiba Satellite P70-A] Brightness Hotkey Doesn't Work

[WinEunuchs2Unix]

Under Kernel 3.13 and 3.15.0-031500-generic the Toshiba hotkeys Fn+F6
and Fn+F7 to control screen brightness (Satellite L300) only work after
manually suspending through the system tray drop down menu and then
resuming.  Note the Suspend Hotkey Fn+F3 only works after manually
suspending and resuming at least once.  Hotkeys are lost on the next
reboot or cold boot.

As a workaround I usually manually suspend and resume immediately after
each boot.

In /usr/rc.local you can echo 3 or 4 to the graphics driver so your
eyeballs don't fry from solar bright screen on boot ups.  That
workaround is documented in many Ubuntu forum threads.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326161

Title:
  [Toshiba Satellite P70-A] Brightness Hotkey Doesn't Work

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1222356] Re: ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message

[WinEunuchs2Unix]

I get the bug in terminal mode with gedit /etc/network/interfaces
(read only mode).

I do NOT get the bug with sudo gedit /etc/network/interfaces or
gksudo gedit /etc/network/interfaces (full permissions)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222356

Title:
  ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility
  bus: Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 925760] Re: Constant warnings from the kernel: Test WP failed, assume Write Enabled

[WinEunuchs2Unix]

Well it did work until I rebooted.  The successful solution was to use
sudo gedit /etc/rc.local and insert the following commnands before the
last line which contains exit 0:

rmmod ums_realtek
modprobe ums_realtek ss_en=0

Note sudo prefix isn't needed because rc.local runs with root
privileges at startup.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925760

Title:
  Constant warnings from the kernel: Test WP failed, assume Write
  Enabled

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 925760] Re: Constant warnings from the kernel: Test WP failed, assume Write Enabled

[WinEunuchs2Unix]

Under Trusty 14.04 LTS 3.13.0-24-generic the ss_en=0 option did not work
on first try.  The file was created but it was empty.  After using gksu
gedit blah blah blah on the file and manually putting the option in it
worked fine.  Thank you very much at getting this annoying undocumented
feature (old tongue for bug) out of the way every time I do a dmesg.

After a million lines of 1. Test failed, 2. Ask for cash (who wouldn't?)
and 3. assume write (everyone assumes they are right) The ss_en=0 was
manually added to the file and then the Remove / reinsert kernel module
was executed.  To prove it works dmesg output is below:

[ 3466.265066] sd 2:0:0:0: [sda] Test WP failed, assume Write Enabled
[ 3466.267309] sd 2:0:0:0: [sda] Asking for cache data failed
[ 3466.267317] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 3474.080808] usbcore: deregistering interface driver ums-realtek
[ 3639.916413] ums-realtek 1-4:1.0: USB Mass Storage device detected
[ 3639.917971] scsi6 : usb-storage 1-4:1.0
[ 3639.918200] usbcore: registered new interface driver ums-realtek
[ 3640.918321] scsi 6:0:0:0: Direct-Access Generic- Multi-Card   1.00 
PQ: 0 ANSI: 0 CCS
[ 3640.918936] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 3640.929692] sd 6:0:0:0: [sda] Attached SCSI removable disk

Can we can close this bug if it moves upstream with ss_en=0 and the SD
ram card reader still works as others state?

- WE2U (WinEunuuchs2Unix)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925760

Title:
  Constant warnings from the kernel: Test WP failed, assume Write
  Enabled

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs