[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2014-03-12 Thread Ivan Larionov
This bug affects 14.04 as well and somehow tracked here https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1169614 2 years bug… -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-10-27 Thread John Clark
** Tags added: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes Status in “network-manager” package in Ubuntu: Fix

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-05-31 Thread sourchier
I still have this bug too. Can't we get rid of NetworkManager if no one wants to fix it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-05-30 Thread John Clark
I can confirm this problem still exists in 13.04 (raring). I'm using Daniel Eckl's patch in comment #49 to work around it, but I modified it to only kill dhclient. It appears that dnsmasq is being terminated properly in 13.04. ** Tags added: raring -- You received this bug notification

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-03-19 Thread Sebastien
Bug still present in kubuntu 13.04, network manager 0.9.8.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes Status in

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-03-19 Thread dooblem
I upgraded to network manager 0.9.8.0, still staying in Quantal. Bug still not present on my system. @Sebastien : you should check the output of lsof (see comment #5). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-03-04 Thread dooblem
I installed the Raring network-manager package (0.9.7.995+git201301311547.17123fc-0ubuntu1) in my Quantal install, and the bug seems gone. Now I just have this displayed at shutdown : nm-dispatcher.action: Caught signal 15, shutting down... Rather than invoking init scripts through /etc/init.d,

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-01-25 Thread djbmister
umount-fix.patch: Best if it is cat /var/run/sendsigs.omit.d/network-manager.dhclient-* As if you have multiple ETH, this will not kill it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2013-01-06 Thread Daniel
This bug also affects Quantal, but I don't know how to mark the bug for this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-12-26 Thread Luigi R.
This bug is still affecting quantal as reported by Sebastien. The workaround #5 works for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-12-26 Thread Daniel Eckl
I fixed it for me in upstart, modifying /etc/init/network-manager.conf. Patch attached. ** Patch added: umount-fix.patch https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+attachment/3468459/+files/umount-fix.patch -- You received this bug notification because you are a

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-11-13 Thread Sébastien Escudier
I have this bug in 12.10 and Network manager version 0.9.6.0-0ubuntu7 /sbin/dhclient and /usr/sbin/dnsmasq are not stopped and / cannot be unmounted -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-11-12 Thread John Clark
** Tags added: quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes Status in “network-manager” package in Ubuntu:

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-10-25 Thread John Clark
I can confirm this bug. I have two systems running 12.10 and both experience this issue. Killing dnsmasq and dhclient in the umountroot script results in a clean shutdown on both systems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-10-21 Thread Daniel Eckl
For some reason, the main issue of this report now hit me. Root cannot be unmounted, because dhclient and dnsmasq is still running at this point (verified by running lsof in umountroot). The order of my init scripts is still fine now, I have S35networking, S40umountfs and S60umountroot, so this

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-21 Thread tuhu
I have a mobile broadband device here. I have also removed modemmanager but the message still appears. I'm thinking to open a new bug-report. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-19 Thread tuhu
I could not open the file of /dev/null, where the output of 'ps p $(pgrep modem-manager) 2/dev/null' went, the error on gedit: Could not open the file /dev/null. /dev/null is not a regular file. But, when I piped it to Desktop, like: ps p $(pgrep modem-manager) 2/root/Desktop , the output showed

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-19 Thread Steven Farmer
You didn't answer my question in #42 above. Type man null to learn how /dev/null works. The ps command produced an error message. Assuming that it wasn't mis-typed, that means that the modem-manager process wasn't running, which is the correct result. That's also consistent with last line in

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-17 Thread tuhu
I have put a sync command on the line 64 of /etc/init.d/sendsigs, Steven. But, the message mount: / is busy still appears. Hope there will be some suggestion from the others then. Thank you for your suggestions so far. -- You received this bug notification because you are a member of Desktop

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-17 Thread Steven Farmer
Tuhu, if you type the following three commands into a terminal window what is printed after each command? sudo stop network-manager initctl status modemmanager ps p $(pgrep modem-manager) 2/dev/null The third command should print something only if modem-manager is still running. It shouldn't be,

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-14 Thread Steven Farmer
The /DEBUG file shows that modem-manager is still running, and at line 114 you can see that the init process has /var/log/upstart/modemmanager open for write. That explains the mount: / is busy message. I would think that modem-manager should have exited before umountroot is run. Looking at

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-13 Thread tuhu
Thanks for the respond Steven, Yes, I did execute it from a terminal in the desktop environment. I have un-checked Available to all users for my active network connection, but, the mount: / is busy message still appears. So, I think my problem is not with the network manager. So, as you

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-13 Thread Steven Farmer
Tuhu, no, I wasn't asking that you run the commands from tty1. Now that you've added the ps and lsof commands to the umountroot script, it should create the text file '/DEBUG' when the system is shut down. Please attach the file /DEBUG. The error message mount: / is busy is being printed by the

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-13 Thread tuhu
Here is the DEBUG file. I have no VMware player installed on my system, the non-Ubuntu applications that are installed in my system are Oracle Virtualbox, remastersys, and nvidia proprietary driver. But, I remember, last time, I installed a dialer and driver for Huawei ec156 USB modem (provided

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-13 Thread tuhu
And, here is something. The message mount: / is busy does not appear each time I power off the system from tty1 while the lightdm is off. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-12 Thread Steven Farmer
Tuhu, your ps output shows quite a lot still running. Did you execute the command from a terminal in the desktop environment? To be helpful, the ps and lsof commands should be run from the /etc/init.d/umountroot script. See message #5 above. Before adding debug commands to umountroot, you

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-06-11 Thread adi
I think I have a problem with this message also on shut down: mount: / is busy. I don't remember when it started to appear. I just realized this messages yesterday. So, I google over looking for answer. I hope here is the right place to ask. Several ways I have tried: 1. I have uninstalled

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Daniel Eckl
I fear I cannot verify this fix :( I'm still suffering from this problem, using: network-manager/precise uptodate 0.9.4.0-0ubuntu4 All the networkmanager stuff wants to terminate AFTER the umountroot script. I used halt to shutdown the sytem without poweroff and made a screenshot to show you

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Daniel Eckl
Additionally I let umountroot make a ps -ef and a lsof -nP just before trying to remount readonly. The output is attached, too (see safe.root.debug.txt) ** Attachment added: ps -ef and a lsof -nP just before trying to remount

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Steven Farmer
Daniel, I notice /etc/rc6.d/S03umountroot stop in your ps output. On my 12.04 installs I have S60umountroot in /etc/rc0.d and /etc/rc6.d. S03 sounds awfully early to me. Try sudo mv /etc/rc6.d/S03umountroot /etc/rc6.d/S60umountroot and then do sudo shutdown -H now and see what happens. -- You

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Mathieu Trudel-Lapierre
Indeed, umountroot is supposed to be at 60; based on how we ship these scripts on a default install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title:

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Mathieu Trudel-Lapierre
umountroot must be at least lower than S35networking; which will emit deconfiguring-networking: that's the stop condition for dbus, which is the stopping condition (stopping dbus) for network-manager. Only once NM is stopped can you safely run umountroot; otherwise the dhclient binaries would

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Daniel Eckl
Thank you so much Mathieu, that was a stunning catch. Something obviously shuffled my rc links around O.o I once (months ago) had the problem that vmware player was changing the position of halt but seemingly it changed a lot more :( Anyway: Obviously my problem is not this bug and I'm now sure

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Steven Farmer
Daniel, try: $ sudo update-rc.d -f umountroot remove $ sudo update-rc.d umountroot start 60 0 6 . Note the period at the end of the 2nd command. And yes, my previous suggestion of using mv won't work, you have to use update-rc.d, sorry. When I used update-rc.d to put umountroot at 03 as you

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Daniel Eckl
Thank you very much. Sadly it turned out that most of the sequence numbers are totally wrong. It's a wonder that still everything worked flawlessly except this unmounting... I searched for a way to set all sequence numbers to their distribution default, but I failed to find such a way. I now

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Daniel Eckl
After fixing all my init script symlinks, this problem is gone. Thank you all so much for your help. Some background information for others who might have my problem: Cause: Installing Vmware Player broke all rc script links. I guess that happened already when still running ubuntu 11.10. See

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Steven Farmer
The perl script /usr/share/sysv-rc/saveconfig prints out the current configuration as a series of update-rc.d commands. If you like, I can send you a copy from a more-or-less vanilla 12.04 install. It can't be completely vanilla without my doing a fresh install in a VM, and I won't volunteer for

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-11 Thread Steven Farmer
Oops, I sent my previous message before I saw yours saying you've fixed things. Congratulations, and thanks for sharing the method - I'll have to remember that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-10 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu4 --- network-manager (0.9.4.0-0ubuntu4) precise-proposed; urgency=low * debian/patches/quit_dhclient_on_exit.patch: make sure we kill dhclient when we are stopping. (LP: #963106) *

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-10 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu4 --- network-manager (0.9.4.0-0ubuntu4) precise-proposed; urgency=low * debian/patches/quit_dhclient_on_exit.patch: make sure we kill dhclient when we are stopping. (LP: #963106) *

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-02 Thread Martin Pitt
Hello Steven, or anyone else affected, Accepted network-manager into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-02 Thread Steven Farmer
After installing network-manager 0.9.4.0-0ubuntu4 from precise-proposed, things are looking good. The root filesystem is clean on reboot even after a reinstall of libc6. Many thanks to Mathieu! -- You received this bug notification because you are a member of Desktop Packages, which is

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-05-02 Thread Jean-Baptiste Lallement
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-27 Thread dino99
it seems that this issue reported here also affect me : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/962113 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title:

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-25 Thread Mathieu Trudel-Lapierre
** Description changed: + [Impact] + On shutdown, dhclient isn't getting reaped by NetworkManager, despite being kept running through sendsigs so as not to disrupt remote filesystems (and their unmounting at shutdown). dhclient may be keeping open files for its lease files, which causes issues

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-23 Thread Mathieu Trudel-Lapierre
Oops, why is this still Incomplete? I've been working on a patch and it's pretty much ready now; so setting to In Progress until an upload to -proposed. ** Changed in: network-manager (Ubuntu Precise) Status: Incomplete = In Progress -- You received this bug notification because you are

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-23 Thread Launchpad Bug Tracker
** Branch linked: lp:~mathieu-tl/network-manager/precise-0sru -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes Status in

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-21 Thread Steve Langasek
I believe the right answer here is that NM should be reaping all of its dhclient helpers on shutdown, including those for wired interfaces. This is the only robust way to handle the system shutdown case, and it makes sense to me that this would be the expected behavior when shutting down NM any

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-19 Thread Terry Newton
On my test systems I fixed this bug by editing /etc/init.d/umountroot and adding... /sbin/killall5 -15 sleep 2 ...just before the part where it remounts the root fs RO. That tells the system to ask all non-kernel tasks to clean up and exit. No idea if this is a proper fix but on my installs it

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-19 Thread camez
I found a solution. But it's bad idea. I added the following line to /etc/rc0.d/S20sendsigs nmcli nm sleep true Because nmcli needs Dbus, nmcli must call before killall. This is to resolve this bug. But another problem occurs. There is umountnfs after this. -- You received this bug

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-13 Thread Mathieu Trudel-Lapierre
These changes were made on purpose in NetworkManager to avoid init killing dhclient before NetworkManager is shut down, which solves slowness at shutdown and also solves a long-time issue with mounted network shares at shutdown. NetworkManager also doesn't stop dhclient by itself on shutdown on

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-13 Thread Steven Farmer
Yes, yes, I understand all of that, there is no need to continue repeating it. Your motivations don't change the fact that, in trying to fix one problem, you've created another. Your changes are causing umountroot to FAIL at shutdown time. -- You received this bug notification because you are

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-13 Thread sourchier
After installing a clean copy of ubuntu-12.04-beta2-dvd-amd64.iso--and applying updates--this bug is still there. I install ed in vmware. I used the same command as Steven Farmer to see the errors in dmseg. -- You received this bug notification because you are a member of Desktop Packages, which

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-12 Thread Mathieu Trudel-Lapierre
I'm unable to reproduce this. On all my systems NetworkManager shuts down cleanly and indeed doesn't stop dhclient, but that's expected behavior, since when you're turning NM off you may wish to retain wired connections, which happens to indeed be the case for users with mounted network shares.

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-12 Thread sourchier
I am using ext2 as a /boot. Also I have a tmpfs mounted as: tmpfs /tmptmpfs nodev,nosuid0 0 Other than that, everthing seems stock. I have installed/deinstalled alot of packages. But debsums seems to find no error. I just wish fsck would learn how to chill.

Re: [Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-12 Thread Steven Farmer
The underlying problem is that, at system shutdown time, dhclient isn't given the opportunity to gracefully exit, closing any files it has open. This causes /etc/init.d/umountroot to fail. When umountroot fails, the filesystem must be recovered. There is, to the best of my knowledge, nothing

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-11 Thread kapetr
Can confirm: after unchecking Available to all users on my wired card: - on shutdown/reboot is now no mount: / is bussy at the end - on boot is now no ext4-fs : fsck required (which BTW in my case had end with no orphans in 9/10 cases) -- You received this bug notification because you are a

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-11 Thread Mathieu Trudel-Lapierre
** Changed in: network-manager (Ubuntu Precise) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title:

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-04-06 Thread Steven Farmer
One last data point: I'm seeing the problem only with wired connections when Available to all users has been checked for that connection (right-click on the nm-applet icon, select Edit Connections..., select the connection and click Edit... then check/uncheck Available to all users in the lower

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-03-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-03-26 Thread Clint Byrum
** Changed in: network-manager (Ubuntu) Importance: Undecided = High ** Changed in: network-manager (Ubuntu) Milestone: None = ubuntu-12.04 ** Also affects: network-manager (Ubuntu Precise) Importance: High Status: Confirmed -- You received this bug notification because you

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-03-26 Thread Clint Byrum
Thanks for the info Steven. I looked into this a bit more. It would seem this bug introduced the omitting: bug #869635 The resolution makes, I think, a false assumption that when network- manager is killed that it will take dhclient with it. This does not seem to be the case. Or, more likely,

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-03-26 Thread Steven Farmer
Clint, I don't see the dhclient process die when network-manager is stopped. But I think I was guilty of some fuzzy thinking in saying that the problem is due to the pid file being held open; the problem is that the dhclient pid file isn't deleted from /var/run/sendsigs.omit.d (so

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-03-26 Thread Kate Stewart
** Tags added: rls-mgr-p-tracking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes Status in “network-manager” package in

[Desktop-packages] [Bug 963106] Re: NetworkManager causes orphaned inodes

2012-03-23 Thread Steven Farmer
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/963106 Title: NetworkManager causes orphaned inodes Status in “network-manager” package in Ubuntu: New Bug description: