No way, it took me way to long to get that up and going last time. I'd
just close it. This bug hasn't gotten any activity at all except for
from me. And, it was a weird idea to begin with. You don't use
enterprise class backup software to backup to gmailfs.
--
Can't use gmailfs as a storage
I have no idea. The bug occurred by upgrading from Dapper to Edgy
because Ubuntu switched to udev in the Edgy release. I have not tried
upgrading a pre-udev system since getting over this problem.
I guess this problem would only be producable under software currently
support by Ubuntu by
I'm running Ubuntu Hardy.
Here are the apt-cache policy's you asked for:
[EMAIL PROTECTED]:/etc$ apt-cache policy bacula
bacula:
Installed: (none)
Candidate: 2.2.8-5ubuntu7
Version table:
2.2.8-5ubuntu7 0
500 http://mirror.anl.gov hardy/main Packages
[EMAIL PROTECTED]:/etc$
Above, note that I've removed bacula from my system since I couldn't get
it to work with gmailfs. I may add it back later.
--
Can't use gmailfs as a storage directory for bacula
https://bugs.launchpad.net/bugs/251268
You received this bug notification because you are a member of Ubuntu
Bugs,
I had to mark this bug private. It contains information that should not
be made public.
I've already resubmitted this bug as #251268.
Please just delete this bug report.
** Visibility changed to: Private
--
Can't use gmailfs as a storage directory for bacula
** Description changed:
+ PLEASE DON'T WASTE TIME READING THIS BUG REPORT. SEE MY FOLLOW UP
+ COMMENT. THIS BUG IS A DUPLICATE.
+
Binary package hint: gmailfs
I'm getting errors about not being able to stat a gmailfs file system
when I try to use one to backup stuff up to using
Public bug reported:
Binary package hint: gmailfs
I'm getting errors about not being able to stat a gmailfs file system
when I try to use one to backup stuff up to using bacula. I believe
this is because of a limitation of gmailfs.
Here's the failure error I'm getting from bacula when I try
** Description changed:
Binary package hint: gmailfs
I'm getting errors about not being able to stat a gmailfs file system
when I try to use one to backup stuff up to using bacula. I believe
this is because of a limitation of gmailfs.
Here's the failure error I'm getting from
Public bug reported:
Binary package hint: gmailfs
I'm getting errors about not being able to stat a gmailfs file system
when I try to use one to backup stuff up to using bacula. I believe this
is because of a limitation of gmailfs.
Here's the failure error I'm getting from bacula when I try
On hardy, I got an error saying something like couldn't find
ClientCookie when I run that last easy_install command Sam mentions.
To get around that error, I had to do a sudo easy_install --upgrade
ClientCookie. Then I could run sudo easy_install --upgrade libgmail
just fine.
--
gmailfs
I just tried this the other day on Gutsy. pdb mode worked fine for me.
I was using the emacs package, not emacs-snapshot.
--
pdb doesn't work in Emacs after upgrading to Feisty
https://bugs.launchpad.net/bugs/114933
You received this bug notification because you are a member of Ubuntu
Bugs,
Okay, I don't understand all the output of 'apt-cache policy'. I
understand it more with your desciption. Having an additional
security+update would be a solution for update-manager.
I'm wondering if there isn't a larger issue though when you consider the
whole of the Ubuntu desktop. In the
** Attachment added: Screenshot-Update Manager.png
http://launchpadlibrarian.net/12976297/Screenshot-Update%20Manager.png
--
update-manager indicates that updates are security updates even if they're not
https://bugs.launchpad.net/bugs/209169
You received this bug notification because you
Public bug reported:
Binary package hint: update-manager
Even if the only updates available are non-security updates, package-
manager makes it visually look like the updates are in fact security
updates.
In the attached screenshot, you can see where at the top of the
updatatable package list,
So, I installed the updates and now there's one new update available.
It's a non-security update and the Important security updates message
is gone. It now says Recommended Updates.
I'm guessing this bug only occurs on new systems where you haven't
installed any certain type of packages yet.
I reported this bug based on information I'd gathered off the Ubuntu
Forums and the mythtv-users mailing list. I was trying to figure out if
it would work or not if I bought it.
It turns out I had misread the USB UIRT web site. They want $50 + $8
shipping, not just $8. The USB UIRT has Windows
Public bug reported:
Binary package hint: linux-image
There was a regression in between 2.6.22 and 2.6.20 that made the USB
UIRT stop working.
The USB UIRT is an infrared transceiver. You plug it into your
computer, and it receives signals from your remote control. This is an
important device
What happens on the box I just built using an old Realtek 8139 card I
had lying around is that the 8139too driver will load. But, after using
the network for a while, the whole computer will hang.
I finally figured out to swap the Realtek 8139 card out for a Linksys
and my computer is running
I just came across this issue in Feisty, apparently its still there.
A workaround I'm using is to place a link in this secure path to the
command I want to run where it already exists on the filesystem.
--
sudo built with --with-secure-path is problematic
https://bugs.launchpad.net/bugs/50797
I tried pdb in the emacs-snapshot and emacs-snapshot-gtk packages. It
doesn't work in those places either.
However, Alexandre Vassalotti is maintaining an emacs package because
he wants custom fonts or something like that. pdb is working for me
with his package. Instructions for installing
and be presented
with a prompt where I could debug my script, as well as an
arrow in another source code buffer indicating where I am in the source code.
Now however, when I do M-x pdb RET pdb ~/grabbers/npr-grabber.py -s
WESUN, I get this is in a buffer called *gud*:
Current directory is /home/levander
Just wanted to add that this bug really shocks me. Aren't there a lot
of Canonical developers using python? Do they just not use emacs or pdb
to debug their code?
That Usenet thread I pointed to has stuff about ipython.el that you can
download from other places on the internet not working also.
Carlos, what I did to fix my system is in the 12/03 00:21 post.
First, the 2.6.17 kernel (which is what Edgy runs) is not installed on
the system. You can do this just by looking at the grub menu on boot.
If 2.6.17 is installed, you don't have the exact same problem I had.
Explaining a little
** Changed in: grub (Ubuntu)
Sourcepackagename: grub = udev
--
Kernel panic after Initializing /dev during startup after /init: 76: Syntax
error
https://launchpad.net/bugs/74009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I modified /etc/fstab and the grub configuration to use /dev/hda files
instead of UUID's. That got the 2.6.12 kernel to boot. There was some
wierdness, like USB would not work, but I was able to use the machine.
After booting 2.6.12, I sudo aptitude install linux-generic to get a
more recent
I made an edgy LiveCD and booted the problem machine with it - boots
fine. It looks like the menu.lst that is installed on the system is
correct. Although, I did make one mistake in typing out the UUID in the
original bug report above. I changed the 5th to last character from a c
to a 6.
Other
I just noticed something. I'm still on the 2.6.12 kernel (as is shown
in the menu.lst excerpt above). With the edgy upgrade, aren't I
supposed to be on 2.6.17?
I originally installed Warty on this machine, and have upgraded through
every Ubuntu release. The only thing I can remember doing
Public bug reported:
What's going on now with my edgy upgrade from dapper (I did use update-
manager) is that when I boot into the recovery mode kernel, it hangs.
The last few lines:
Begin: Initializing /dev...
/init: 76: Syntax error: 0xID=4bd43095-7d5e-4829-95dd-25bb7860664
[4294680.075000]
Public bug reported:
Binary package hint: xtoolwait
the xtoolwait binary is installed in /usr/X11R6/bin/xtoolwait. This
directory is not in the PATH by default. And, the only other file in
that directory is a link to /usr/bin/X. I'm guessing xtoolwait should
go in /usr/bin/X11, which is a
29 matches
Mail list logo
