Public bug reported:
Traceback (most recent call last):
File "/usr/bin/ubiquity", line 130, in ?
install(sys.argv[1])
File "/usr/bin/ubiquity", line 55, in install
ret = wizard.run()
File "/usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py", line 266,
in run
self.proces
My apologies; I was in kind of a hurry last night. Attaching now.
** Attachment added: "My /var/log/syslog"
http://librarian.launchpad.net/3206147/syslog
** Attachment added: "My /var/log/installer/syslog"
http://librarian.launchpad.net/3206148/syslog
** Attachment added: "My /var/log/part
*** This bug is a duplicate of bug 13851 ***
Apparently this is the known xfs/grub issue. This is a major
showstopper, and it seemed to happen even when I tried again using the
default ext3 setup. Trying again with / xfs and /boot ext2.
--
Installer failure
https://launchpad.net/bugs/51559
--
u
*** This bug is a duplicate of bug 13851 ***
Yes, this is the known issue. /boot ext2 (first partition) and / xfs
(second partition), and a 1gb swap partition as 3rd partition installed
fine.
Marking as duplicate. PLEASE warn people about this :)
** This bug has been marked a duplicate of bug 13
** Bug 51559 has been marked a duplicate of this bug
--
Grub will not install to XFS Formatted Partition
https://launchpad.net/bugs/13851
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 47848 ***
I'm sure I saw Reiser support when I was installing the other day. But
what is it you mean that you can't safely add a separate boot partition?
That's how I got around the XFS crashy-crashy (I used ext2, don't need a
journal on something that's rarely u
On 19-Jul-06, at 3:15 PM, Carthik Sharma wrote:
> *** This bug is a duplicate of bug 47848 ***
>
> Thanks for your report. Due to some reliability problems with GRUB and
> XFS, you need to use a non-XFS root filesystem or create a non-XFS /
> boot
> filesystem. Bug 47848 is filed to note that th
unsubscribe [EMAIL PROTECTED]
--
should warn at partitioning stage if /boot is on XFS
https://launchpad.net/bugs/47848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
(Sorry if I'm doing this wrong, there's just no bloody unsubscribe link
- dwf)
--
should warn at partitioning stage if /boot is on XFS
https://launchpad.net/bugs/47848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
It's infuriating is what it is. I sorted through every bug in the
"duplicates" column, found the one I'd submitted and unsubscribed from
it, and now I'm still receiving notifications. That's good enough reason
for me to never submit a bug report again.
--
should warn at partitioning stage if /boo
t2000kw raises a good point, though I think even if scanners aren't
involved, full and flawless support for devices whose function is
specifically enabling disabled users to use their computer (i.e. USB
braille devices) should be of *paramount* priority. I haven't read the
SABDFL's statement but I'
FWIW my affected device's ID is: 04a9:220e Canon, Inc. CanoScan
N1240U/LiDE 30, if some sort of exclude list is being compiled, as was
intimated a few posts ago.
Also, on a different note: I think it might be a little hard to compile
yourself a kernel to get your USB braille device working... if y
Confirmed on Feisty i386. This bug report is going on 9 months old, and
the extremely simple fix has been around for as long, how long is it
going to take?
--
"Address already in use" error with multiple downloads
https://bugs.launchpad.net/bugs/57039
You received this bug notification because yo
It seems this problem was fixed in a recent package upgrade.
** Changed in: evolution (Ubuntu)
Status: Unconfirmed => Fix Released
--
Sent messages not saved to remote folder if remote folder doesn't belong to
same account
https://bugs.launchpad.net/bugs/118343
You received this bug noti
Can you elaborate on what you mean by "forcibly reboot after syncing"?
I removed the asound.state file, ran 'kill $(lsof -t /dev/dsp*
/dev/audio* /dev/mixer* /dev/snd/*) && sudo modprobe -r $(lsmod|awk
'/^snd/ {print $1}') && sudo modprobe snd-emu10k1', and I still see no
'PCM' slider in alsamixer
I should note that I see "PCM Front, PCM Center, PCM Surround" etc. but
last I checked they don't seem to do anything.
--
[regression] Feisty has no separate PCM slider in mixer on an Audigy 2 Platinum
PCI
https://bugs.launchpad.net/bugs/110939
You received this bug notification because you are
Public bug reported:
Binary package hint: evolution
Basically, I have one account that I check mail from, and several set up
to send mail from, as I have a few different email addresses that all
get forwarded to that one IMAP account but that I use for different
things (my work address, my school
I have to voice agreement with pinus and Markus. I realize the Ubuntu
devs are really committed to meeting a release schedule, and I can
definitely respect that, but going to release with this kind of major
known regression is bad, BAD karma. Maybe they weren't aware how
widespread these scanners a
Public bug reported:
Binary package hint: nautilus
Essentially, two of my PATA partitions that mount okay have phantom
entries in the nautilus sidebar, that I recognize by their sizes as
being /media/RAID and either /home or /media/storage.
If it makes any difference my /media/RAID partition is
Oh, I also created a fresh user account to test whether it was a problem
with my assorted gnome preferences. Same thing appears.
--
After Feisty upgrade: some drives show up twice in nautilus, once unmounted and
once mounted
https://bugs.launchpad.net/bugs/109418
You received this bug notificati
Public bug reported:
After upgrading to feisty boots take a long time, it's stuck at the very
first position of the progress bar, and this seems to be what's causing
it:
[ 29.128243] ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma
0x0001ffa8 irq 15
[ 29.798376] ata2.00: ATAPI, ma
Experiencing the same bug. Canon LiDE 30.
Like "Kev" above, I nearly THREW OUT my scanner because I assumed it had
taken some sort of fatal blow. It's kind of bizarre that they'd allow
this kind of regression to go into the stock kernel. I agree, laptop
suspend/resume is important, but Jesus, if y
To elaborate, the really devious thing about this bug is that it can
EASILY be mistaken for a hardware fault, especially since everything
appears to function normally on the software end. Please AT LEAST
release a quick and dirty "OMFG you got a crap scanner sry" patch.
Joel Berger's plustek-wrapp
gscan2pdf refuses to scan in lineart mode. "Unknown message: scanimage:
unrecognized option `--compression=None'"
Considering how this is the most useful mode for document scanning I
wouldn't consider this a very good workaround.
--
Canon Lide25 (plustek backend) scanner does not scan via gui
ht
Public bug reported:
Basically, in Volume Control for my Audigy 2 Platinum [SB0240P] I've
lost the ability (since the upgrade from Edgy) to control PCM level
separate from the Master level. I don't see a PCM slider, if I go to
Edit->Preferences I see PCM and it's already selected, but deselecting
** Attachment added: "dmesg"
http://librarian.launchpad.net/7461317/dmesg
--
[regression] Feisty has no separate PCM slider in mixer on an Audigy 2 Platinum
PCI
https://bugs.launchpad.net/bugs/110939
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: "asound.state"
http://librarian.launchpad.net/7461320/asound.state
--
[regression] Feisty has no separate PCM slider in mixer on an Audigy 2 Platinum
PCI
https://bugs.launchpad.net/bugs/110939
You received this bug notification because you are a member of Ubuntu
Bugs, wh
As described in Bug 96826 "irqpoll" added to grub's menu.lst works for
me.
--
ATA errors cause LONG boot time in Feisty
https://bugs.launchpad.net/bugs/109130
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I had the same problem with my Sony drive and 'irqpoll' works for me.
--
Feisty Beta does not recognise CD burner
https://bugs.launchpad.net/bugs/96826
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
@Kai Blin: Can you please confirm the kernel version this was happening
with?
--
corruption of large files reported with linux 2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Currently (as of 11.04, and I suspect in 11.10), pitivi breaks if you
have another Python executable on your PATH, e.g. using virtualenv or a
custom-built Python. As per the Debian Python Policy (I can't find a
similar document for Ubuntu other than some poorly maintained wiki
Public bug reported:
Currently (as of 11.04, and I suspect in 11.10), hplip will potentially
break if you have a non-system Python executable on your PATH, e.g.
using virtualenv or a custom-built Python. As per the Debian Python
Policy (I can't find a similarly thorough document for Ubuntu),
> Th
*** This bug is a duplicate of bug 912625 ***
https://bugs.launchpad.net/bugs/912625
This affects several more packages, so I've created a bug at the
distribution level, #912625.
** This bug has been marked a duplicate of private bug 912625
--
You received this bug notification because you
*** This bug is a duplicate of bug 912625 ***
https://bugs.launchpad.net/bugs/912625
This affects several packages so I've created a distribution-level bug,
#912625.
** This bug has been marked a duplicate of private bug 912625
--
You received this bug notification because you are a member
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912625
Title:
#!/usr/bin/env python breaks Python-based Ubuntu packages in the
presence of virtualenvs, local install
Marc: Fair enough. I guess the same kind of hijacking I mentioned could
be accomplished in a lot of ways, including setting PYTHONPATH, so it's
probably alright.
Scott: The Debian policy reads:
> Maintainers should not override the Debian Python interpreter using
/usr/bin/env
The word "should" i
36 matches
Mail list logo
