Verified for me in 8.10 final.
--
Bookmarks/Recent Files menuitems are not updated
https://bugs.launchpad.net/bugs/148768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
Confirmed here too on an integrated ATI Radeon HD 3200. Winston is right
that this only seems to happen in fullscreen: changing any games to run
in windowed mode causes no corruption. OpenGL screensavers also cause
this problem.
--
Corruption (ambiguous) of the Screen in a GLX game [EPR#257842]
I still experience this bug in Intrepid final using KDE 4.1.3 (but also
experienced it in 4.1.2). It seems to go beyond duplex and copy number,
as I just started a print job specifying only pages 3 - 4 in kate, and
got all 4 pages instead. I've not tried this with other documents or KDE
programs si
Confirmed here too! Updating to the newest driver in proposed as
suggested worked. Fullscreen gaming, here I come!
--
Corruption (ambiguous) of the Screen in a GLX game [EPR#257842]
https://bugs.launchpad.net/bugs/289628
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: gscan2pdf
It appears that attempting to save a djvu file scanned at a resolution
of 600 dpi fails in gscan2pdf 0.9.26. I'm not sure when the bug first
appeared, as this is the first time I have tried to save a djvu file at
this resultion.
Running gscan2p
Thank, I understand. I tried looking through the code myself to see if I
could change how the values are read, but I couldn't figure out where
you read in the values for the resolution from the frontend help! There
goes my knowledge of perl.
I will just wait patiently for the fix. Thanks again.
-
Working here too. No flashing LED for me, because I don't think mine is
supposed to :p
Glad to see this got fixed. Thanks for all the hard work!
--
linux-backports-modules-2.6.24-21-generic causes kernel panic when unloading
Intel Wireless driver
https://bugs.launchpad.net/bugs/251252
You recei
I have experienced this bug ever since 8.04, and I still do in 8.10 with
the latest updates. The % at which it hangs varies (sometimes 80%, 97%,
and sometimes the progress bar turns completely blank.) QComicBook must
be killed as it becomes completely unresponsive.
In 8.10, I have even experienced
I just had this problem today and posted a comment on the bug filed
upstream (http://bugs.kde.org/show_bug.cgi?id=140443#c5). This bug most
definitely exists as it has affected me once before (as I mentioned in
my comment), but I did not report the bug since I could not reproduce
it. I still do not
I can confirm this bug still occurs in Fiesty and KDE 3.5.6, but ONLY
when Google Suggest is on. If GS is on for only Google searches, the bug
will only happen when searching with Google in the search bar; and for
all searches when GS is turned on for all searches.
If there's anything I can do to
running "sudo update-desktop-database -v 2>&1|grep invalid" resulted in
no output, so I am not sure if this is the problem (at least for me). I
will just wait for updated debs since I am not knowledgeable enough to
apply patches and build packages for myself.
If there's any thing someone like a ty
I believe I may have solved my problem as kbuildsycoca4 no longer
crashes, but I have yet to try logging into kde4.
I did not get output using the command above, but I did try running
kbuildsycoca4 again in the terminal and I took note of all files which
it claimed were not compliant with the XDG
KDE4 works now for me as well on both of my machines. It is probable
that the Swiftfox.desktop file is guilty because I had deleted mine
while I was editing the rest for the missing semicolon. I deleted it
because it was left over from a previous installation even though I had
uninstalled it.
Coul
Confirmed here too, after the same update.
Same error output at the end when I run kbuildsycoca4 in the terminal.
--
kbuildsycoca4 aborts after upgrade KDE 4.0.1 -> 4.0.2
https://bugs.launchpad.net/bugs/199145
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fedora includes the winepulse patch by default, that counts for
something. (Granted they are lagging behind a few wine releases)
http://koji.fedoraproject.org/koji/buildinfo?buildID=155086
--
Ubuntu should ship wine with the wine-pulse patches
https://bugs.launchpad.net/bugs/437749
You received
I too experience this issue in a production environment with NFS4
mounted home directories and autofs in Karmic 9.10 with all the latest
updates.
If a user logs in with GNOME and later logs out, subsequent users
attempting to log in (with GNOME, KDE, etc even terminals) experience a
hang instead.
** Also affects: byobu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998812
Title:
status area missing since 5.18
To manage notifications about this bug
OK so I had to trim /var/kern/log a bit...because it ballooned up to
400+ MB. Hope that its ok that I cut it down to about 4.3MB. It was
pretty much repeating itself after that point.
Also there was absolutely no video this time (and no audio, but I know
you said we'd work on that later).
** Atta
Sure hope the clue as to why video didn't work wasn't at around megabyte
399 or something! (Also, typo in my previous comment: of course I meant
/var/log/kern.log)
OK, I will post my results as soon as I get them for all three kernels.
This may take a while so maybe by/before the weekend.
Thanks!
Not sure if this is your problem Martin, but this could happen if you
are updating grub-pc, or running update-grub, as a user with a
Kerberized NFS home directory. If you are anywhere in the home
directory, and use sudo to run those commands, then you will get errors
like the above (if local root i
I was wondering, exactt, what hardware are you using? I've been seeing
this problem on my girlfriend's desktop, which is using an nVidia-based
motherboard.
I can't give you all the exact lspci output right now, but I was
beginning to suspect the problem might have something to do with the
chipset.
And here's what I promised from my side from my girlfriend's desktop. I
will attach the output of lspci -vvv, dmesg output when the webcam is
attached, and dmesg when attempting to use the cam.
I will include lsusb output for the webcam here inline:
Bus 002 Device 005: ID 046d:08f5 Logitech, Inc.
dmesg output when camera is plugged in, and then an attempt is made to
use it.
Cheese was used in this instance, in the following two ways:
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so cheese
and as just
cheese
Forcing use of the 32-bit library for v4lcompat.so (as recommended with
skype -- just i
@Lee
I'll try to get you the requested info with the new kernel in a bit.
There are several things plugged into usb, including a bluetooth dongle,
a printer, a mouse, a keyboard, and the occasional ipod. No hub here.
However, the webcam works flawlessly when the computer is booted into
Windows on
Whoops, looks like something might be wrong with that kernel image
This happens when you try to install it:
(Reading database ... 326215 files and directories currently installed.)
Unpacking linux-image-2.6.32-26-generic (from
linux-image-2.6.32-26-generic_2.6.32-26.45_amd64.deb) ...
Done.
dpkg-d
OK, news: I successfully installed your provided kernel on that machine,
rebooted without the camera plugged in, unplugged everything except
keyboard and mouse, did
tail -f /var/log/messages
and tee'd that to another file, then plugged in the camera. This happened:
Oct 8 09:11:18 lilypad kernel:
Sure, sorry about before!
OK attached is the entire dmesg output (this stuff didn't seem to be
logged right to /var/log/messages or /var/log/dmesg).
If there's anything else I can provide, machine's still on, booted to
this kernel, cam plugged in.
The camera was recognized, by the way, with no c
I've heard that part mentioned in the past, about USB bandwidth being
used up, but I just think its curious that its basically happening only
on this board (for me)!
Thanks for your help, though, and whatever you guys come up with, I'm
sure it'll be a great help and I know it took a lot to get her
Lee, sorry for the long response. I've got word back about the camera
situation. The new kernel patches appear to have worked! Although the
camera does not work as a microphone (but I think this may have been
intentional on your part? If I'm not mistaken, your custom kernel has no
usb sound drivers
OK I've installed the new kernel you posted and got the udev log you
wanted.
Also, I figured out what was wrong with the usb audio: I had blacklisted
it on that machine before on advice I had seen somewhere else regarding
webcam issues! It should be fine now.
I also have the dmesg output and will
Well, as promised, here are the /var/log/kern.log's for each of those
kernels. Also, as for the video and audio in each one, the results are
as follows:
100: Full video, no problems. Audio did not work (device never recognized by
Pulseaudio).
200: Half video screen. Audio did not work (device nev
** Attachment added: "/var/log/kern.log for 200 kernel, including messages when
using Skype"
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1709316/+files/kern_log_lee_kernel_200
--
Logitech Quickcam Messenger is not usable
https://bugs.launchpad.net/bu
** Attachment added: "/var/log/kern.log for 300 kernel, including messages when
using Skype"
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1709317/+files/kern_log_lee_kernel_300
--
Logitech Quickcam Messenger is not usable
https://bugs.launchpad.net/bu
Sorry again for the delay. I don't actually have much physical access to
this machine and do most things remotely and by instructing someone
else.
OK, so here's the dmesg output, taken while the camera was being used
with Skype.
Video is chopped in half horizontally: top half has video, bottom ha
Sorry Lee, but I think that the output you're referring to is what I had
posted in comment #78. That was with only the cam plugged in (except
keyboard and mouse, unless you wanted me to unplug one or both of those
as well).
Re: the patch -- great news!
--
Logitech Quickcam Messenger is not usabl
35 matches
Mail list logo
