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

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

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

It would be nice to have the patch applied both the standard call from bash as well as the python libraries (2.7.12 and 3.x). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu.

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

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

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

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: $

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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]

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

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`:

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

#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 optional

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

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

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

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

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

@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

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

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

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

@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

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

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

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

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

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

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`

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

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

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

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

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

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

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

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

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

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