Sure - the attached output is with the /var/tmp tmpfs line disabled in
fstab (which is the only way I can boot). Not sure which way you wanted
it. But you will see /var/tmp mounted in there because it is currently
mounted from a mount command in rc.local. If you prefer it another way
just let
I need to see it failing in the log ;-)
That makes sense, but I don't know how to do that. I tried disabling kdm start
so I booted into a shell. I then enabled the /var/tmp line in fstab and ran
mountall. In that case it seemed to mount /var/tmp okay, although it did hang.
I had to press
Also, in my above comment where I said
In that case it seemed to mount /var/tmp okay, although it did hang.
I should add that it did NOT display waiting for tmpfs when it hung -
it just seemed to stop without reporting any problem, and Ctrl-C got out
of it. I have only seen mountall (or
The bug that was originally reported has been fixed.
It hasn't been fixed at all, it's just been ignored and listed as fixed,
like many bugs lately, to get it off the buglist quick.
Mounting /var on tmpfs is not a supported configuration for Ubuntu;
/var/lib must be persistent.
What does that
At any rate, for those who actually want to use the capabilities of their OS
and protect their SSD, I have posted a method here which works around this bug
in mountall to some extent.
http://ubuntuforums.org/showpost.php?p=8232599postcount=11
I guess in these days of Microsoft's... excuse me,
*** This bug is a duplicate of bug 459642 ***
https://bugs.launchpad.net/bugs/459642
Can you explain why this was marked as a duplicate of
https://bugs.launchpad.net/bugs/459642 Is there an implicit 'bind'
mount when trying to mount /var/log to tmpfs?
That bug has been marked won't fix
Public bug reported:
Binary package hint: mountall
Mounting tmpfs to /var/log or /var/tmp in fstab causes mountall to hang
at boot with the message waiting for tmpfs
This bug is present in karmic final but was not present in karmic alpha3
and prior. Mounting tmpfs to /tmp does NOT cause this
If log writes are an issue for you, you may want to send them
elsewhere instead of killing them on reboot. (see the syslog-ng manpage,
for instance, on how to do this; you can do it securely)
Thanks for that suggestion - I'll take a look. Generally I don't need
persistent logs, and if there's a
That's odd because on mine /tmp mounts okay with tmpfs - it's just /var
and var/subdir that seems to be affected. I don't have an explicit
/proc/bus/usb mount, just /proc.
FYI you can mount /var/tmp in /etc/rc.local as an alternative. Details in the
SSD CHANGES section here...
** Changed in: mountall (Ubuntu)
Status: Fix Released = New
--
separate /var and /var/tmp tmpfs dependency loop
https://bugs.launchpad.net/bugs/431040
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug does not appear to be fixed in karmic final. Attempting to
mount tmpfs to /var or /var/log in fstab results in a hung waiting for
tmpfs at boot. This was NOT the case in karmic alpha3 and prior, so
perhaps it is the use of upstart that is triggering this problem?
Mounting tmpfs to /tmp
I can confirm this on kubuntu karmic final. This bug was NOT present in
karmic alpha3, so perhaps the use of upstart is responsible? Mounting
tmpfs to /tmp does NOT cause this problem, just /var or a /var subdir.
To reproduce, add this line to fstab:
tmpfs /var tmpfs
Public bug reported:
Binary package hint: mplayer
As distributed by ubuntu for many versions (hardy and perhaps earlier),
including the current 2:1.0~rc3+svn20090426-1ubuntu4, gmplayer rapidly
and continuously displays pop-up error messages (often far too fast to
read) for trivial errors such as
As this wish has been ignored for over a year, I have submitted it here as a
bug to be ignored...
https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/412669
Meanwhile, does anyone have any suggestions for an alternate and fairly
easy means of installing a *functional* gmplayer in (K)ubuntu?
*** This bug is a duplicate of bug 409962 ***
https://bugs.launchpad.net/bugs/409962
This has now been fixed...
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/409962
--
Only blank pages print on Brother MFC-7420
https://bugs.launchpad.net/bugs/410556
You received this bug notification
This duplicate bug has a list of printers and error logs...
https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/410556
--
poppler 0.11.2 produces blank pages with cups
https://bugs.launchpad.net/bugs/409962
You received this bug notification because you are a member of Ubuntu
Bugs, which
Confirmed - downgrade to libpoppler5_0.11.0-0ubuntu4_amd64.deb solved
this problem - thanks!
--
Only blank pages print on Brother MFC-7420
https://bugs.launchpad.net/bugs/410556
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I also recall seeing the CUPS-Add-Modify-Printer: Unauthorized
messages as Tim Bosse reported above, although both the cups html
interface and the KDE printer config utility seemed to add, remove and
modify the printer without complaint.
Also, here is the ppd file for the Brother MFC-7420...
**
Public bug reported:
Binary package hint: ghostscript
My Brother MFC-7420 BW laser printer will only print blank pages in
karmic. This printer worked flawlessly with the Brother-supplied driver
on Kubuntu Hardy and Intrepid, 32 and 64 bit, KDE3 and KDE4.
Further, I have two MFC-7420s, one
As a followup, several people have reported that the workaround above
for replacing wodim does correct this, although in my case I had a
physically bad drive that had to be replaced (which confusingly produced
the same error). Step-by step-instructions are in this post...
Also confirmed with a Brother printer on Kub 8.0.4.1. system-config-
printer-kde is indeed the correct package because removing it got rid of
this annoying applet. That applet was also the only thing on my system
causing python to be loaded all the time. What is Kubuntu thinking
using such a
Also FWIW, I've been speaking with the maintainer of libburnia and
xfburn, and he says libburn and cdrskin are replacements for wodim and
cdrecord and are built on a fresh codebase. He wrote: Cdrskin can
replace cdrecord (even for k3b, just make a symlink from cdrecord -
cdrskin) [or really from
My suggestion: change broken fork wodim to the original cdrtools...
here is what worked for me. Use at your own risk.
Replacing wodim with the genuine cdrtools (tested on Kubuntu hardy)
The issue:
http://cdrecord.berlios.de/private/linux-dist.html
If you are not running the original software,
My suggestion: change broken fork wodim to the original cdrtools...
here is what worked for me. Use at your own risk.
Replacing wodim with the genuine cdrtools (tested on Kubuntu hardy)
The issue:
http://cdrecord.berlios.de/private/linux-dist.html
If you are not running the original software,
Same problem with a recent fresh install of Kubuntu Hardy/KDE3. The
problem does not appear to be a kernel bug, but a misconfiguration in
/etc/udev/rules.d/70-persistent-cd.rulesThe system-wide fix for this
is available here...
http://ubuntuforums.org/showpost.php?p=5014367postcount=4 The
After I print, the document stays in the job list saying 'processing',
even though it printed successfully. If I try to cancel it I get
client-error-not-possible. The job list can be cleared with: sudo
lprm -
Hardy Kubuntu with Brother 7420. I did not have this problem with
Feisty.
--
cups
Confirmed on up-to-date Kubuntu Hardy with KDE3 and nvidia-glx driver.
Logout produces a blank screen. If I press Ctrl-Alt-F1 that terminal
appears blank, but if I press enter the Login: prompt does come up. ps
-Af reveals that the user was logged out. No errors in the X log.
Ctrl-Alt-F7
Following instructions on
https://help.ubuntu.com/community/BinaryDriverHowto/ATI#head-
99489608eb537a1a0346cdd3ad34209d7887714a (for Feisty) I installed the
latest ATI driver 8.39.4 (for Radeon Xpress 200M) and this bug/problem
seems no longer there... Only a frozen mouse cursor but that's maybe
Tried 8.37.6 on Feisty/KDE using bryce's packages - no change in the
problem. Logging out or attempting a shutdown/restart always results in
a frozen screen of garbage. I guess I'll hold my breath and wait for
ATI to test their junk drivers on their hardware.
--
log out or switch user results
vax_fortran said
The equivalent modifications to KDM are:
1. Open /etc/kde3/kdm/kdmrc
2. Search for uncomment the line TerminateServer=True (or just add this
line, if there is no comment).
This worked for me on 32-bit Kubuntu Feisty, with Radeon Xpress200M
Graphics Chipset (on a Compaq V2000Z,
I have this with a new Kubuntu Feisty install with an ATI Mobility
Radeon X300, 2.6.20-15-generic. I installed the latest ATI 8.36.5 with
a manual build. I do not have beryl installed. Logging off a session
(except a full restart), suspend, and hibernate are affected. I seem to
be able to
Tried again... For the record, I first upgraded the -10 kernel and
headers, but didn't install anything for -11, including the new nvidia-
glx. Rebooted and all was well.
Then I installed the -11 offerings in Adept. Rebooted and X failed to
start. Then in console
sudo apt-get install
I'm using Kubuntu Edgy with a GeForce 6200TD 128M AGP. I recently did a
kernel update through Adept Notifier and X wouldn't start. Got the
error running install command for nvidia. I rolled the system back
using a partition image I had, so now I'm back to the pre-upgrade point.
Here is what I
33 matches
Mail list logo
