May 21, 2018 19:54
That warning is a good sign that it already started the daemon, so you don't need to start it again. Did the semi-transparent popup with the claret red background not appear? Still old opaque popup? You can customize the popup via above mentioned notifyconf tool
May 21, 2018 19:49
I see, you don't have .notify-osd configuration file. Let me post mine: pasted.co/3cb75d0e. First create a file touch ~/.notify-osd then open it with gedit: gedit ~/.notify-osd then paste the settings in the link, save and exit. Files and folders beginning with a dot are hidden. By the way /usr/lib/x86_64-linux-gnu/notify-osd is a daemon, so it must keep running. System must start it automatically at start up but something goes wrong in your system.
May 21, 2018 19:49
It seems that /usr/lib/x86_64-linux-gnu/notify-osd daemon not launching. Try to run it from terminal /usr/lib/x86_64-linux-gnu/notify-osd
May 21, 2018 19:49
OK, what's the output of pgrep -af notify* again? And try notify-send -u normal "Hello" "Testing"
May 21, 2018 19:49
What's the output of pgrep -af unity-settings-daemon? Restart your comp at first.
May 21, 2018 19:49
you must install those dependencies: sudo apt-get install debhelper dh-autoreconf gnome-common intltool libdbus-1-dev libdbus-glib-1-dev libglib2.0-dev libgtk-3-dev libnotify-dev
May 21, 2018 19:49
Did you build the package via dpkg-buildpackage -b -uc? In your case the built deb package name may be different. Try this dpkg -i notify-osd_0.9.35+15.04.20150126-0ubuntu1-leolik*.deb
May 21, 2018 19:49
cd Notify-OSD; chmod +x ./autogen.sh; dpkg-buildpackage -b -uc then install the notify-osd_0.9.35+15.04.20150126-0ubuntu1-leolik~ppa3_i386.d‌​eb package via dpkg -i notify-osd_0.9.35+15.04.20150126-0ubuntu1-leolik~ppa3_i386.d‌​eb in the parent directory of Notify-OSD
May 21, 2018 19:49
I noticed that notify-osd does not exists in the repo, you can build it from source. Here is the source code https://github.com/khurshid-alam/Notify-OSD, you can install notify-osd customization tool bzr branch lp:notifyconf; cd notifyconf; make and run the tool ./notifyosdconf
May 21, 2018 19:49
You need to install libnotify sudo apt-get install libnotify-bin for notify-send
May 21, 2018 19:49
Try to reinstall sudo apt-get install --reinstall notify-osd and check if it works with notify-send -u normal "Hello" "Testing"
May 21, 2018 19:49
what's the output of pgrep -af notify?
May 21, 2018 19:49
Did you install another desktop environment, such as Mate?
 
Apr 18, 2017 19:57
There is a way to install Ubuntu in a directory, it's called booting into chroot. But it's sophisticated for a newbie. You need to debootstrap installation via internet thegeekstuff.com/2010/01/… then install ubuntu desktop and kernel, and install grub bootloader. Finally you need to apply this patch github.com/lemonsqueeze/boot_chroot
 

 Discussion between kos and kenn

Imported from a comment discussion on askubuntu.com/questions/...
Feb 16, 2016 13:19
@kos Thank you for all your efforts. I must say that your support encouraged me to work on it at length. Though that unbuffer workaround works, I am not satisfied with it, but my knowledge about debugging is limited.
Feb 15, 2016 22:09
@kos Yes I reinstalled both of them
Feb 15, 2016 15:54
@kos Yes I forgot to add it, I am using 14.04.3 32 bit
Feb 15, 2016 13:47
apt-cache policy grep
grep:
Installed: 2.16-1
Candidate: 2.16-1
Version table:
*** 2.16-1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
100 /var/lib/dpkg/status
Feb 15, 2016 13:46
apt-cache policy bash
bash:
Installed: 4.3-7ubuntu1.5
Candidate: 4.3-7ubuntu1.5
Version table:
*** 4.3-7ubuntu1.5 0
500 http://archive.ubuntu.com/ubuntu/ trusty-security/main i386 Packages
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages
100 /var/lib/dpkg/status
4.3-6ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
Feb 15, 2016 13:23
you are the master and I need your help. 9c96f6ac51aaf5deb8043d8c2330da69 /bin/bash and b0ce14813cf497a45c894d73fa309ba8 /bin/grep
Feb 15, 2016 13:23
GNU bash, version 4.3.11 and grep (GNU grep) 2.16
Feb 15, 2016 13:23
Right, I noticed that just after I posted the output. Above code gives me development tail: write error: Broken pipe tail: write error
Feb 15, 2016 13:23
Sometimes it just runs well but it often fails
Feb 15, 2016 13:23
Sorry, I spoke too early, it fails
Feb 15, 2016 13:23
hey, it works :) how?
Feb 15, 2016 13:23
ls -lt $PWD| grep -m 1 ^d | cut -b 51- still gives me the same error development ls: write error: Broken pipe :(
Feb 15, 2016 13:23
Thank you for responding. How can I apply it to my particular case for ls -lt $PWD| grep ^d | head -1 | cut -b 51- and generalize it?
 

 Discussion between A.B. and kenn

Imported from a comment discussion on askubuntu.com/questions/...
Nov 14, 2015 12:43
thank you
Nov 14, 2015 12:43
ok
Nov 14, 2015 12:43
Thanks for your help
Nov 14, 2015 12:42
it only removed mpv
Nov 14, 2015 12:42
it looks ok now
Nov 14, 2015 12:42
I had to reinstall libavcodec-extra-54 but now I could remove it successfully
Nov 14, 2015 12:36
Nov 14, 2015 12:34
it ended successfully
Nov 14, 2015 12:33
I ran "sudo dpkg -r --force-all libavformat54" and it removed a bunch of interdependent packages then I ran "sudo apt-get install -f"
Nov 14, 2015 12:31
I think I fixed it
Nov 14, 2015 12:03
Unfortunately apt-get install -f gives dependency errors :(
Nov 14, 2015 11:52
all the best!
Nov 14, 2015 11:51
have a good day
Nov 14, 2015 11:51
Thank a lot
Nov 14, 2015 11:50
I am grateful
Nov 14, 2015 11:50
Would you post it as an answer ?
Nov 14, 2015 11:49
Thank you A.B
Nov 14, 2015 11:48
shall I run "apt-get install -f" ?
Nov 14, 2015 11:48
Nov 14, 2015 11:46
ok
Nov 14, 2015 11:46
is it all?
Nov 14, 2015 11:46
it installed without error
Nov 14, 2015 11:45
downloaded