[Bug 998812] Re: status area missing since 5.18
** 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 go to: https://bugs.launchpad.net/byobu/+bug/998812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673438] Re: update-grub: cannot restore the original directory
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 is not given root privileges on the NFS mount). I just encountered this bug myself and it prevented grub-pc from updating. This shouldn't be a show-stopper: grub-pc should report that grub was installed correctly and just print a warning that it couldn't cd back to the original directory, as other packages seem to do. For example, openoffice.org-emailmerge didn't fail, but just said this: Setting up openoffice.org-emailmerge (1:3.2.0-7ubuntu4.2) ... cd: 84: can't cd to /home/yozen and continued. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673438 Title: update-grub: cannot restore the original directory -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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 never recognized by Pulseaudio). 300: Only a small sliver of video across the top made it through. Audio did not work (device never recognized by Pulseaudio). So the audio never worked, but at least in the 100, video seems to have worked perfectly. I will attach each file successively. ** Attachment added: /var/log/kern.log for 100 kernel, including messages when using Skype https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1709315/+files/kern_log_lee_kernel_100 -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
** 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/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
** 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/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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! -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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). ** Attachment added: kern.log, trimmed https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1702516/+files/kern_log_lee_kernel -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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 half is black. Quickcam does not show up as a capture device, so there is no way for Skype or something to capture audio. Checking lsmod shows that snd_usb_audio is indeed loaded, but it still doesn't work. ** Attachment added: dmesg output with latest kernel, while running Skype. https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1697393/+files/dmesg_lee_kernel -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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 post that too if you need it. ** Attachment added: var_log_udev_lee_kernel https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1693096/+files/var_log_udev_lee_kernel -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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). In any case, attached is the dmesg output, including that while the camera was used (about 3 times). ** Attachment added: dmesg_lee_kernel_patched https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1691745/+files/dmesg_lee_kernel_patched -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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 usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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: [ 621.850038] usb 2-8: new full speed USB device using ohci_hcd and address 8 Oct 8 09:11:18 lilypad kernel: [ 622.083800] usb 2-8: configuration #1 chosen from 1 choice Oct 8 09:11:18 lilypad kernel: [ 622.167463] Linux video capture interface: v2.00 Oct 8 09:11:18 lilypad kernel: [ 622.182881] gspca: main v2.7.0 registered Oct 8 09:11:18 lilypad kernel: [ 622.199060] Lee - NULL - Enter Oct 8 09:11:18 lilypad kernel: [ 622.199110] Lee - ^C - Enter Oct 8 09:11:18 lilypad kernel: [ 622.199113] STV06xx: Probing for a stv06xx device Oct 8 09:11:18 lilypad kernel: [ 622.199117] Lee - ^C - Enter Oct 8 09:11:18 lilypad kernel: [ 622.199119] gspca: probing 046d:08f5 Oct 8 09:11:18 lilypad kernel: [ 622.199124] Lee - ^C - Enter Oct 8 09:11:18 lilypad kernel: [ 622.199126] STV06xx: Configuring camera Oct 8 09:11:18 lilypad kernel: [ 622.199129] Lee - NULL - Enter Oct 8 09:11:18 lilypad kernel: [ 622.199131] STV06xx: st6422 sensor detected Oct 8 09:11:18 lilypad kernel: [ 622.199134] Lee - NULL - Enter Oct 8 09:11:18 lilypad kernel: [ 622.199136] STV06xx: Initializing camera Oct 8 09:11:18 lilypad kernel: [ 622.450062] Lee - NULL - Enter Oct 8 09:11:18 lilypad kernel: [ 622.450165] PGD aa4b9067 PUD a4290067 PMD 0 Oct 8 09:11:18 lilypad kernel: [ 622.450186] CPU 2 Oct 8 09:11:18 lilypad kernel: [ 622.450189] Modules linked in: gspca_stv06xx(+) gspca_main videodev v4l1_compat v4l2_compat_ioctl32 rfcomm sco bridge binf mt_misc stp bnep l2cap vboxnetflt vboxdrv snd_hda_codec_via ipt_REJECT ipt_LOG xt_limit xt_tcpudp ipt_addrtype xt_state snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy ip6table_filter snd_seq_oss ip6_tables snd_seq_midi nf_nat_irc snd_rawmidi nf_conntrack_irc snd_seq_midi_eve nt nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 snd_seq nf_conntrack_ftp nf_conntrack snd_timer snd_seq_device iptable_filter ppdev nvidia(P) btusb ip_ tables lp snd parport_pc psmouse vga16fb edac_core soundcore vgastate serio_raw bluetooth i2c_nforce2 edac_mce_amd snd_page_alloc usblp x_tables parport fbco n tileblit font bitblit softcursor uvesafb usbhid hid floppy sata_nv forcedeth pata_amd Oct 8 09:11:18 lilypad kernel: [ 622.450286] Pid: 9542, comm: modprobe Tainted: P 2.6.32-26-generic #45 MCP61M05 Oct 8 09:11:18 lilypad kernel: [ 622.450291] RIP: 0010:[812b93d9] [812b93d9] strnlen+0x9/0x40 Oct 8 09:11:18 lilypad kernel: [ 622.450299] RSP: 0018:8800a4327978 EFLAGS: 00010086 Oct 8 09:11:18 lilypad kernel: [ 622.450303] RAX: 8170c16a RBX: 81999fc0 RCX: 0002 Oct 8 09:11:18 lilypad kernel: [ 622.450307] RDX: 1440 RSI: RDI: 1440 Oct 8 09:11:18 lilypad kernel: [ 622.450310] RBP: 8800a4327978 R08: 0073 R09: Oct 8 09:11:18 lilypad kernel: [ 622.450314] R10: 0005 R11: R12: 81999bc6 Oct 8 09:11:18 lilypad kernel: [ 622.450318] R13: 1440 R14: R15: Oct 8 09:11:18 lilypad kernel: [ 622.450323] FS: 7f715d9f2700() GS:88002830() knlGS: Oct 8 09:11:18 lilypad kernel: [ 622.450327] CS: 0010 DS: ES: CR0: 8005003b Oct 8 09:11:18 lilypad kernel: [ 622.450330] CR2: 1440 CR3: bf85c000 CR4: 06e0 Oct 8 09:11:18 lilypad kernel: [ 622.450334] DR0: DR1: DR2: Oct 8 09:11:18 lilypad kernel: [ 622.450338] DR3: DR6: 0ff0 DR7: 0400 Oct 8 09:11:18 lilypad kernel: [ 622.450343] Process modprobe (pid: 9542, threadinfo 8800a4326000, task 88011aa316e0) Oct 8 09:11:18 lilypad kernel: [ 622.450349] 8800a43279b8 812bb2d0 81999bc6 Oct 8 09:11:18 lilypad kernel: [ 622.450355] 0 a0c213c8 a0c213c6 8800a4327b28 81999fc0 Oct 8 09:11:18 lilypad kernel: [ 622.450362] 0 8800a4327a58 812bc360 0004 000a Oct 8 09:11:18 lilypad kernel: [ 622.450376] [812bb2d0] string+0x40/0x100 Oct 8 09:11:18 lilypad kernel: [ 622.450383] [812bc360] vsnprintf+0x310/0x5f0 Oct 8 09:11:18 lilypad kernel: [ 622.450392] [812bc306] ? vsnprintf+0x2b6/0x5f0 Oct 8 09:11:18 lilypad kernel: [ 622.450399] [812bc751] vscnprintf+0x11/0x30 Oct 8 09:11:18 lilypad kernel: [ 622.450409] [81066a40] vprintk+0xb0/0x470 Oct 8 09:11:18 lilypad kernel: [ 622.450418] [81541364] printk+0x41/0x45 Oct 8 09:11:18
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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 crash in modprobe like last time. ** Attachment added: dmesg output using kernel provided by Lee. https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1679098/+files/dmesg_lee_kernel -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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 here. Thanks. -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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. QuickCam Messenger Communicate and this is the message produced by *any* program trying to use the webcam, always from l4v: libv4l2: error turning on stream: Input/output error This is all on an x86_64 machine running Ubuntu Linux 10.4.1 with KDE, on a quad-core AMD processor with an nVidia MCP61 based chipset. ** Attachment added: Output of lspci -vvv https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1676973/+files/lspci_vvv -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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 in case!), still gives the libv4l message given in my previous comment. ** Attachment added: dmesg output when plugging in camera and attempting to use it with cheese https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070/+attachment/1676977/+files/dmesg_plugin_cam_and_use -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
@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 this machine, with all of those devices plugged in simultaneously. There might be something with how the kernel is handling usb bandwidth on this and other boards, but we'll save that for when I get the debugging output. Thanks for the help, I'll get back to you in a few. -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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-deb (subprocess): short read in buffer_copy (failed to write to pipe in copy) dpkg-deb: subprocess paste returned error exit status 2 dpkg: error processing linux-image-2.6.32-26-generic_2.6.32-26.45_amd64.deb (--install): short read in buffer_copy (backend dpkg-deb during `./lib/modules/2.6.32-26-generic/kernel/drivers/video/nvidia/nvidiafb.ko') Running postrm hook script /usr/sbin/update-grub. Generating grub.cfg ... Found linux image: /boot/vmlinuz-2.6.32-25-generic Found initrd image: /boot/initrd.img-2.6.32-25-generic Found linux image: /boot/vmlinuz-2.6.32-24-generic Found initrd image: /boot/initrd.img-2.6.32-24-generic Found memtest86+ image: /boot/memtest86+.bin Found Windows 7 (loader) on /dev/sda1 Found Microsoft Windows XP Professional on /dev/sdb1 done Errors were encountered while processing: linux-image-2.6.32-26-generic_2.6.32-26.45_amd64.deb In case there's something wrong with the download, here's the md5sum I got: dc75edc2c10c1dfb804ce67572f997cf Downloads/linux-image-2.6.32-26-generic_2.6.32-26.45_amd64.deb -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22070] Re: Logitech Quickcam Messenger is not usable
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. The same webcam works on two Intel-based machines and my own ATI-based machine, all of them running the latest version of Lucid, all up to date (yes, I even tried again after the last kernel update). I'll send the lspci, dmesg, and error output as soon as I get a chance, but so far this seems to be an issue only on her machine. -- Logitech Quickcam Messenger is not usable https://bugs.launchpad.net/bugs/22070 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 437749] Re: Ubuntu should ship wine with the wine-pulse patches
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299649] Re: evolution-data-server's process still here after logout
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. The solution in that case is to kill e-d-s processes, and in some cases kill anything using files in /home and restart autofs. This is a serious problem for me if users have trouble logging in like this. Here is the evolution process I see when I use lsof | grep home to see what is accessing the home directories (username removed): evolution 10673 USER 24u REG 0,2612288 1262460 /home/USER/.evolution/addressbook/local/system/addressbook.db evolution 10673 USER 25r REG 0,26 196 1262461 /home/USER/.evolution/addressbook/local/system/addressbook.db.summary So at least in my case, access to the address book in evolution is never given up, causing problems for subsequent logins. There are users who use Evolution, so uninstalling it might not be an option. -- evolution-data-server's process still here after logout https://bugs.launchpad.net/bugs/299649 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225588] Re: qcomicbook hangs when opening zip archives
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 it hanging with .rar's (progress bar is blank in these cases) and the only way I can use QComicBook is by unarchiving the file and opening the folder with it. I'll see if I can get a sample document up, but it should occur with any zip archive of jpgs, (or any rar of jpgs, for me). Running qcomicbook in a terminal gives absolutely no output. -- qcomicbook hangs when opening zip archives https://bugs.launchpad.net/bugs/225588 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148768] Re: Bookmarks/Recent Files menuitems are not updated
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289628] Re: Corruption (ambiguous) of the Screen in a GLX game [EPR#257842]
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286014] Re: kde print ignores duplex copy options
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 since I'd rather not waste any more paper. -- kde print ignores duplex copy options https://bugs.launchpad.net/bugs/286014 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 289628] Re: Corruption (ambiguous) of the Screen in a GLX game [EPR#257842]
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] https://bugs.launchpad.net/bugs/289628 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 283847] [NEW] Saving a djvu file with a resolution of 600 dpi fails in gscan2pdf v0.9.26
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 gscan2pdf with the '--debug' option shows that the error is related to giving cjb2 an invalid value for the -dpi option: cjb2 -dpi 600dpi /home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/4iEtfzxnzr.pnm /home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/ZQ2WVcMpXW.djvu CJB2 --- DjVuLibre-3.5.20 Simple DjVuBitonal encoder Usage: cjb2 [options] input-pbm-or-tiff output-djvu Options are: -verboseDisplays additional messages. -dpi nSpecify image resolution (default 300). -clean Cleanup image by remove small flyspecs. -lossy Lossy compression (implies -clean as well) -losslevel n Loss factor (implies -lossy, default 100) Encoding is lossless unless a lossy options is selected. djvused '/home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/ZQ2WVcMpXW.djvu' -e 'select 1; set-txt djvusedtxtfile' -s *** [1-12311] Failed to open document 'file://localhost/home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/ZQ2WVcMpXW.djvu' *** (DjVuDocEditor.cpp:187) *** 'void DJVU::DjVuDocEditor::init(const DJVU::GURL)' *Note: I changed my temporary directory because my / partition wasn't big enough for many temp files Saving a document scanned at a resolution of 300 dpi does not cause this issue, and I assume the same is true for resolutions below that: cjb2 -dpi 300 /home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/R07iQ1Yt72.pnm /home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/6fxnuQ8uMZ.djvu djvused '/home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/6fxnuQ8uMZ.djvu' -e 'select 1; set-txt djvusedtxtfile' -s djvm -c '/home/yozen/Documents/Important PDFs/cut scanned filename.djvu' /home/yozen/FATTY_FAT/gscan2tmp/MHY243AhAK/6fxnuQ8uMZ.djvu Process 11666 exited. Removing 'dpi' from '600dpi' should fix the problem (that's why I assumed it was only 600 dpi which had problems). This issue does not arise when saving to pdf, nor when scanning with scanimage (I did not test with scanadf). ** Affects: gscan2pdf (Ubuntu) Importance: Undecided Status: New -- Saving a djvu file with a resolution of 600 dpi fails in gscan2pdf v0.9.26 https://bugs.launchpad.net/bugs/283847 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 283847] Re: Saving a djvu file with a resolution of 600 dpi fails in gscan2pdf v0.9.26
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. -- Saving a djvu file with a resolution of 600 dpi fails in gscan2pdf v0.9.26 https://bugs.launchpad.net/bugs/283847 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251252] Re: linux-backports-modules-2.6.24-21-generic causes kernel panic when unloading Intel Wireless driver
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158978] Re: kmail deleted contents of inbox with dimap
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 know how it happens, but it seems like it does this when it has trouble connecting. Now, KMail crashes when attempting to refresh the IMAP cache, preventing me from even using it. I am running Hardy with KDE 3.5.9, all up-to-date. Please let me know if I can provide more information (and how to get it). The mail SEEMS to just have the inbox label removed from it, so it is only visible under All Mail or any other label it has, and I did not see it in the trash. -- kmail deleted contents of inbox with dimap https://bugs.launchpad.net/bugs/158978 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199145] Re: kbuildsycoca4 aborts after upgrade KDE 4.0.1 - 4.0.2
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 standard and which were in the ~/.local/share/applications folder. I noticed that for all of those it said they were missing a trailing semicolon in the MimeType list. I opened all of the files it mentioned that were only in that directory, and added a semicolon to the end of the MimeType line in each. I saved all of the files and ran kbuildsycoca4 again. I still got the error with files in the folder /usr/share/applications/ but those did not seem to cause a problem. I even realized I missed one file (googleearth.desktop) which it still complained about, but no crash. Instead, it just says that it parsed those files and then it ends without problems. I will try logging into KDE4 later and will try this on a different machine as well. This is a very strange problem which may crop up again if you change the MimeTypes of some applications, of maybe if you update one of those problematic programs' packages and they ship with non-compliant .desktop files. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199145] Re: kbuildsycoca4 aborts after upgrade KDE 4.0.1 - 4.0.2
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. Could more people please post their success with just trying to delete that file, please? This bug may not be a problem in kde4libs at all. Or it may be, but only due to some weird formatting in that particular file. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199145] Re: kbuildsycoca4 aborts after upgrade KDE 4.0.1 - 4.0.2
running sudo update-desktop-database -v 21|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 typical end-user can do to help, I would be willing to do it. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199145] Re: kbuildsycoca4 aborts after upgrade KDE 4.0.1 - 4.0.2
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 23535] Re: Writing cursor moving to end of line when editing
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 provide more information on the bug, please tell me and I'll do the best I can. -- Writing cursor moving to end of line when editing https://bugs.launchpad.net/bugs/23535 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
