[Touch-packages] [Bug 1392725] Re: cups (or lubuntu printer assistant) fills /tmp with a huge number of files
This seems to be exactly the bug fixed in debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764472 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253 It confirms it's a system-config-printer bug, not cups Any chance of seeing a backport in ubuntu ? ** Bug watch added: Debian Bug tracker #764472 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764472 ** Bug watch added: Debian Bug tracker #764253 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764253 ** No longer affects: cups (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1392725 Title: cups (or lubuntu printer assistant) fills /tmp with a huge number of files Status in “system-config-printer” package in Ubuntu: New Bug description: On lubuntu 14.10, after a boot problem described here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637 I was trying to find out what generated a huge number of files in /tmp. Although it is difficult to even ls into this directory. "find ." ended up starting to list some files (deleting those files is being difficult too). I ended up looking at one of them and it seems that cups (or the lubuntu default printer assistant) is the culprit. user:fulltmp$ file ./546285ff50f53 ./546285ff50f53: symbolic link to `/etc/cups/ppd/freebox.ppd' What I did is the following : I tried to add a network printer (named freebox) using the printer assistant, this gave me some errors such as "cups failed with the following message : Success" (if memory serves). The printer would not be added, so I ended up adding it directly through the cups web interface, which worked. Sorry I do not know which step could have generated this "huge" number of files. Am deleting them as we speak using an rsync trick I found here https://unix.stackexchange.com/questions/37329/efficiently-delete- large-directory-containing-thousands-of-files (but it's still been a few hours). The only size "evaluation" I have of this fulltmp is through "ls -alh /" which reports 262M. 262M of symlinks, anyone estimate how many symlinks that makes ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1392725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392725] Re: cups (or lubuntu printer assistant) fills /tmp with a huge number of files
** Also affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1392725 Title: cups (or lubuntu printer assistant) fills /tmp with a huge number of files Status in “cups” package in Ubuntu: New Status in “system-config-printer” package in Ubuntu: New Bug description: On lubuntu 14.10, after a boot problem described here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637 I was trying to find out what generated a huge number of files in /tmp. Although it is difficult to even ls into this directory. "find ." ended up starting to list some files (deleting those files is being difficult too). I ended up looking at one of them and it seems that cups (or the lubuntu default printer assistant) is the culprit. user:fulltmp$ file ./546285ff50f53 ./546285ff50f53: symbolic link to `/etc/cups/ppd/freebox.ppd' What I did is the following : I tried to add a network printer (named freebox) using the printer assistant, this gave me some errors such as "cups failed with the following message : Success" (if memory serves). The printer would not be added, so I ended up adding it directly through the cups web interface, which worked. Sorry I do not know which step could have generated this "huge" number of files. Am deleting them as we speak using an rsync trick I found here https://unix.stackexchange.com/questions/37329/efficiently-delete- large-directory-containing-thousands-of-files (but it's still been a few hours). The only size "evaluation" I have of this fulltmp is through "ls -alh /" which reports 262M. 262M of symlinks, anyone estimate how many symlinks that makes ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1392725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392725] [NEW] cups (or lubuntu printer assistant) fills /tmp with a huge number of files
Public bug reported: On lubuntu 14.10, after a boot problem described here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637 I was trying to find out what generated a huge number of files in /tmp. Although it is difficult to even ls into this directory. "find ." ended up starting to list some files (deleting those files is being difficult too). I ended up looking at one of them and it seems that cups (or the lubuntu default printer assistant) is the culprit. user:fulltmp$ file ./546285ff50f53 ./546285ff50f53: symbolic link to `/etc/cups/ppd/freebox.ppd' What I did is the following : I tried to add a network printer (named freebox) using the printer assistant, this gave me some errors such as "cups failed with the following message : Success" (if memory serves). The printer would not be added, so I ended up adding it directly through the cups web interface, which worked. Sorry I do not know which step could have generated this "huge" number of files. Am deleting them as we speak using an rsync trick I found here https://unix.stackexchange.com/questions/37329/efficiently-delete-large- directory-containing-thousands-of-files (but it's still been a few hours). The only size "evaluation" I have of this fulltmp is through "ls -alh /" which reports 262M. 262M of symlinks, anyone estimate how many symlinks that makes ? ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1392725 Title: cups (or lubuntu printer assistant) fills /tmp with a huge number of files Status in “cups” package in Ubuntu: New Bug description: On lubuntu 14.10, after a boot problem described here https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637 I was trying to find out what generated a huge number of files in /tmp. Although it is difficult to even ls into this directory. "find ." ended up starting to list some files (deleting those files is being difficult too). I ended up looking at one of them and it seems that cups (or the lubuntu default printer assistant) is the culprit. user:fulltmp$ file ./546285ff50f53 ./546285ff50f53: symbolic link to `/etc/cups/ppd/freebox.ppd' What I did is the following : I tried to add a network printer (named freebox) using the printer assistant, this gave me some errors such as "cups failed with the following message : Success" (if memory serves). The printer would not be added, so I ended up adding it directly through the cups web interface, which worked. Sorry I do not know which step could have generated this "huge" number of files. Am deleting them as we speak using an rsync trick I found here https://unix.stackexchange.com/questions/37329/efficiently-delete- large-directory-containing-thousands-of-files (but it's still been a few hours). The only size "evaluation" I have of this fulltmp is through "ls -alh /" which reports 262M. 262M of symlinks, anyone estimate how many symlinks that makes ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1392725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392637] Re: Cannot boot with newly installed systemd if /tmp/ is filled with files
** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1392637 Title: Cannot boot with newly installed systemd if /tmp/ is filled with files Status in “systemd” package in Ubuntu: New Status in “upstart” package in Ubuntu: New Bug description: On a new lubuntu 14.10 install, after installing a bunch of new packages, I rebooted the machine and it stalls on startup. It stays on the four dots of plymouth (not the graphical version). After trying various options in rescue mode, I end up understanding that the boot system has switched to systemd by looking at /var/log/dpkg.log (attached). I then tried init=/lib/systemd/systemd in grub without quiet and splash and found that it was blocking on "a start job is running for Create Volatile files and directories". A search on the internet later, I found that the problem was solved by this approach : http://forums.debian.net/viewtopic.php?f=10&t=118008 So, in rescue mode, I did a mv /tmp/ to /fulltmp/ (an ls wouldn't return so I'm guessing the /tmp/ is really full and the disk is not rocket fast). I recreated /tmp and did a chmod 1777 /tmp, reboot and it works! While describing this, am not entirelly sure upstart is exempt from this bug (how do I check which init was used after I've booted ?) This is a very frustrating bug since it doesn't appear on startup even when removing quiet or splash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392637] [NEW] Cannot boot with newly installed systemd if /tmp/ is filled with files
Public bug reported: On a new lubuntu 14.10 install, after installing a bunch of new packages, I rebooted the machine and it stalls on startup. It stays on the four dots of plymouth (not the graphical version). After trying various options in rescue mode, I end up understanding that the boot system has switched to systemd by looking at /var/log/dpkg.log (attached). I then tried init=/lib/systemd/systemd in grub without quiet and splash and found that it was blocking on "a start job is running for Create Volatile files and directories". A search on the internet later, I found that the problem was solved by this approach : http://forums.debian.net/viewtopic.php?f=10&t=118008 So, in rescue mode, I did a mv /tmp/ to /fulltmp/ (an ls wouldn't return so I'm guessing the /tmp/ is really full and the disk is not rocket fast). I recreated /tmp and did a chmod 1777 /tmp, reboot and it works! While describing this, am not entirelly sure upstart is exempt from this bug (how do I check which init was used after I've booted ?) This is a very frustrating bug since it doesn't appear on startup even when removing quiet or splash. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dpkg.log" https://bugs.launchpad.net/bugs/1392637/+attachment/4260400/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1392637 Title: Cannot boot with newly installed systemd if /tmp/ is filled with files Status in “systemd” package in Ubuntu: New Bug description: On a new lubuntu 14.10 install, after installing a bunch of new packages, I rebooted the machine and it stalls on startup. It stays on the four dots of plymouth (not the graphical version). After trying various options in rescue mode, I end up understanding that the boot system has switched to systemd by looking at /var/log/dpkg.log (attached). I then tried init=/lib/systemd/systemd in grub without quiet and splash and found that it was blocking on "a start job is running for Create Volatile files and directories". A search on the internet later, I found that the problem was solved by this approach : http://forums.debian.net/viewtopic.php?f=10&t=118008 So, in rescue mode, I did a mv /tmp/ to /fulltmp/ (an ls wouldn't return so I'm guessing the /tmp/ is really full and the disk is not rocket fast). I recreated /tmp and did a chmod 1777 /tmp, reboot and it works! While describing this, am not entirelly sure upstart is exempt from this bug (how do I check which init was used after I've booted ?) This is a very frustrating bug since it doesn't appear on startup even when removing quiet or splash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1392637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 666921] Re: (Kubuntu) GTK app freeze when some GUI feature is used
Am getting something similar to this but don't known where to start debugging it. Removing libcanberra-gtk-module doesn't fix the problem. Doing a $ lsof | grep libcanberra gets me a bunche of matches on files from libcanberra0. Trying to remove that offers to install a bunch of new packages, but removes a number of other things I use. Am using trusty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/666921 Title: (Kubuntu) GTK app freeze when some GUI feature is used Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: Hi, here is my first bug report here: Every GTK application on my Kubuntu 10.10 (x64) successfully upgraded from 10.04 (2 days ago, before everything ok) freezes when I try to use some GUI feature -- checkbox (when "checking" not unchecking), radio buttons when changing radio, and in gtk "filebrowser" dialog when changing the directory. libgtk2.2-0 (2.22.0-0ubuntu1) KDE 4.51 One core of CPU goes to 100% imidiately. Occurs in Pidgin, Gimp, Eclipse, wicd, wireshark No problem in Qt apps. Everything fine if I start this apps as root! Problem appeared after upgrade. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgtk2.0-0 2.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Tue Oct 26 21:15:11 2010 InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, user) LANG=cs_CZ.utf8 SHELL=/bin/bash SourcePackage: gtk+2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/666921/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
