Public bug reported:
After upgrading from 11.10, runit failed to install and, I guess, init
left instead.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: runit (not installed)
ProcVersionSignature: Ubuntu 3.2.0-56.86-generic-pae 3.2.51
Uname: Linux 3.2.0-56-generic-pae i686
Public bug reported:
Hello, have a nice day, and here's my story.
===
I have installed mediatomb on my Debian box and configured it.
I have added lots of stuff there (approx. 700 Gb) of content.
===
I have enabled UPNP plugin in banshee.
Banshee recognized my MediaTomb service and
Public bug reported:
Really no sound
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: alsa-base 1.0.24+dfsg-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-20.34-generic-pae 3.0.30
Uname: Linux 3.0.0-20-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003795
Title:
[To Be Filled By O.E.M., VIA VT1818S, Green Line Out, Rear] No sound
at all
To manage notifications about this bug go to:
adamski, if possible - try to renew (actually change) firmware. For a couple
of times. I got such troubles with Karmik on my Acer Aspire One 8Gb SSD.
Then many times zeroed it, ten (or more) times one-by-one firmwared - and
now it's running fine. Jaunty.
2010/2/24 adamski a...@hasselbalch.com
It's told here in launchpad, that this bug has a patch. But I cannot see
it in usual way - there are instructions, but no patch. Can anyone write
a patch-script to work this problem around??
--
devkit-disks-probe-ata-smart causes HSM Violations on SSD, and potential
hardware death
BTW I've tried reinstalling - but not purging! Trying...
Unsuccessfull =(
2009/12/27 Dave Walker d...@damcconsulting.com
Юрий Аполлов:
Have you tried uninstalling and reinstalling the package?
sudo apt-get purge -f djvulibre-bin sudo apt-get install djvulibre-
bin
--
ddjvu -format=pdf
Walker d...@damcconsulting.com
Юрий Аполлов:
I am sorry but I do not believe your problem qualifies as a bug. This
appears to be a configuration issue and should be handled via one of the
many support methods available to Ubuntu users. I am also happy to
convert this to a question and post your
Strange, but true: I've installed djvulibre-bin on liveusb - and it
successfully converted my djvu to pdf and I was able to read it! So, it's
somewhere in my system - but how can I guess where???
It's bug anyway, and it's gotta be gone =)
So, I'm ready to listen to guesses. I can give you
Ok, I'll attach it now. And I got a difference in a more user-friendly way.
It's in:
stream
q 923.7600 0. 0. 696.2400 0. 0. cm /Im1 Do Q
Actually in signs of point (.). In bad file there are comma (,) signs. That's
the reason, I guess. And I found the difference there (in the
Got same in 9.04
Workaround from #2 solves the problem
Attaching diff from bad (addindb001~) and good (addindb001), made by
find /home/mc-scrat/.tomboy/addin-db-001~/ -type f | xargs cat addindb001~
Hope it helps solving the trouble
--
Tomboy enters infinite loop of errors on start
diff from broken and working $(find /home/mc-scrat/.tomboy/addin-
db-001~/ -type f | xargs cat addindb001~)
** Attachment added: diff.lzma
http://launchpadlibrarian.net/37048708/diff.lzma
--
Tomboy enters infinite loop of errors on start
https://bugs.launchpad.net/bugs/243387
You received
Public bug reported:
When making
ddjvu -format=tiff in.djvu out.tiff
and then
tiff2pdf out.tiff -o out.pdf
everything goes right and outgoing pdf is readable. But when it's made in a way
ddjvu -format=pdf in.djvu out.pdf
then a blank document is the result. Actually, not fully blank: there are
** Attachment added: diff.big-from-small
http://launchpadlibrarian.net/37071323/diff.big-from-small
--
ddjvu -format=pdf makes blank documents
https://bugs.launchpad.net/bugs/499324
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Stephen, try badblocks -wvs /dev/sda to make check your drive in read-write
mode
2009/12/11 Stephen O sogles...@yahoo.com
I had not zeroed my drive prior to installing Fedora 12 so I attempted to
follow Andrew's suggestion (#91). Unfortunately every time I try dd
if=/dev/zero of=/dev/sda
Such an interesting thing: if only I launch parted from liveusb - I
immediately got our errors. Got same using cfdisk. And - it may be
interesting and important - it happens when I just run parted, when I exit
parted - and when I run/exit cfdisk too.
BUT!
Once I've removed libparted and all
Btw libata.dma=3 do not make SSD work in DMA mode though!
There's something to be told to developers, cause I stay on Jaunty so far
this stall goes away!
2009/12/8 Gav Mack gavin...@hotmail.com
Setting libata.dma=3 to grub seems to have stopped the hang on my AAO so
far, the entries in dmesg
A small thing to keep in mind:
1. I load Karmic - and got this bug. Kernel 2.6.31 as to my mind
2. I load Karmic and 2.6.32 - still got this bug
3. I load Jaunty - and got not this bug. Kernel 2.6.28
4. I load Jaunty and 2.6.32 - and got NOT this bug
Though it's NOT a kernel bug I guess. Otherwise
I'm about to please somebody to look distinctly at upstart - can it be
removed (I have no info now on this - I'm still on 9.04). Can somebody try
removing?
2009/12/9 Raf 4283...@noduck.org
What about the increased parallelism in the new upstart? Could this be
the cause of the problems:
2 Scott:
How could it be: same program (here I mean kernel version), same hardware -
and different behaviour on different systems of Ubuntu. Don't you think that
it would be rather strange, if 2 things work here and not there - than it's
not because that things gone bad, and the reason is
And yes- it's in libata!!
SSD is eating brains only when libata.dma=4
http://www.kernel.org/doc/Documentation/kernel-parameters.txt
libata.dma= [LIBATA] DMA control
libata.dma=0 Disable all PATA and SATA DMA
libata.dma=1 PATA and SATA
Telling kernel libata.force=noncq during boot-time from liveUSB had no
effect for me - still got hangups on the same place. It is interesting, that
this happens only after X and gdm is starting. Don't know why really.
Now I got this: booting into single-user mode gave an interesting
result:after
*** This bug is a duplicate of bug 445852 ***
https://bugs.launchpad.net/bugs/445852
** This bug has been marked a duplicate of bug 445852
SSD stall during boot
--
Installing Karmic 20090917 on Acer Aspire One freezes on detecting filesystems
https://bugs.launchpad.net/bugs/432497
You
Btw it's not a kernel trouble - I've made a vanilla kernel, but ssubj hasn't
gone. Strange.
And 9.04 works fine (that's where I'm writing this).
First I decided it's my HDD's problem (I got same errors when it was
uncorrectly firmwared), but it's not - Jaunty shows nice performance. Neither
24 matches
Mail list logo
