[Bug 275691] Re: Flash Printing Doesn't Work in Firefox
Just for reference, I have updated the previously opened bug at adobe with this information here: http://bugs.adobe.com/jira/browse/FP-1853 -- Flash Printing Doesn't Work in Firefox https://bugs.launchpad.net/bugs/275691 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 275691] Re: Flash Printing Doesn't Work in Firefox
I think I should have been more clear above... I couldn't print to any cups printers from the flash applet, neither actual printers nor the cups PDF printer. I was trying to print to PDF from the flash applet at the time I was looking at this issue, but after specifying a default printer in cups, printing to any printer from a flash applet now works, default or not. It doesn't seem to matter which is the default but there has to be a default printer in cups. -- Flash Printing Doesn't Work in Firefox https://bugs.launchpad.net/bugs/275691 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 275691] Re: Flash Printing Doesn't Work in Firefox
I was having the exact same problem described in this bug while trying to print a different Flash applet display using the applet context menu. I enabled cups debug logging and kept noticing a message about cups having no default printer set (which is supposedly just informational). However, I tried setting the cups PDF printer as the default on a whim and it worked. I can now print from Flash applets where I never could before. Specifically I edited /etc/cups/printer.conf and changed the PDF printer definition line from: to: and then restarted cups and it worked. -- Flash Printing Doesn't Work in Firefox https://bugs.launchpad.net/bugs/275691 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 153194] Re: kontact navigator toolbar won't stay when moved
This seems to have been fixed in Gutsy, as it is no longer a problem for me now. ** Changed in: kdepim (Ubuntu) Status: New => Invalid -- kontact navigator toolbar won't stay when moved https://bugs.launchpad.net/bugs/153194 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 204010] Re: networking not working
*** This bug is a duplicate of bug 218126 *** https://bugs.launchpad.net/bugs/218126 Takahito: I tried your latest kernel (linux-image-2.6.24-19-xen_2.6.24-19.33~zng1_amd64.deb) but it did not solve the domU networking problem. Like the stock Hardy kernel, the guest OS does not receive any network traffic using it. Using your older kernel (linux- image-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb) works great, all networking is functioning. Thank you. -- networking not working https://bugs.launchpad.net/bugs/204010 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 156612] Re: filesystem corruption on xfs using sata_sil (sil3114)
Sorry, I can't test this issue further since I had to return the controller card. -- filesystem corruption on xfs using sata_sil (sil3114) https://bugs.launchpad.net/bugs/156612 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156612] Re: filesystem corruption using sata_sil (sil3114)
Title/summary should be changed to: filesystem corruption using sata_sil (sil3114) I have now confirmed corruption on jfs filesystem as well using the same sil3114 based controller as above. This was much harder to bring about, but while copying approximately 50 GB data to a new jfs partition, after about 80% complete I started getting errors indicating that the filesystem was read only, however mount showed the partition as still mounted rw. This is what dmesg had at the same time: [82557.508000] JFS: nTxBlock = 4031, nTxLock = 32255 [88523.472000] ERROR: (device md2): diAllocBit: iag inconsistent [97670.892000] non-latin1 character 0x6c65 found in JFS file name [97670.908000] mount with iocharset=utf8 to access [97670.924000] non-latin1 character 0x7562 found in JFS file name [97670.94] mount with iocharset=utf8 to access [97670.952000] non-latin1 character 0x6d6f found in JFS file name [97670.972000] mount with iocharset=utf8 to access [97670.984000] non-latin1 character 0x766f found in JFS file name [97671.00] mount with iocharset=utf8 to access [97671.016000] non-latin1 character 0x6c65 found in JFS file name [97671.032000] mount with iocharset=utf8 to access [97671.048000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 0 [97671.088000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 1 [97671.112000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 2 [97671.136000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 3 [97671.16] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 4 [97671.184000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 5 [97671.208000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 6 [97671.232000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 7 [97671.256000] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 8 [97671.28] ERROR: (device md3): JFS:Dtree error: ino = 386012, bn=36233131, index = 9 Since my initial report I have also tried a different brand/size SATA harddrive connected to this SATA controller, and had the same result. -- filesystem corruption on xfs using sata_sil (sil3114) https://bugs.launchpad.net/bugs/156612 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156612] Re: filesystem corruption on xfs using sata_sil (sil3114)
** Changed in: linux-source-2.6.22 (Ubuntu) Sourcepackagename: None => linux-source-2.6.22 -- filesystem corruption on xfs using sata_sil (sil3114) https://bugs.launchpad.net/bugs/156612 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156612] filesystem corruption on xfs using sata_sil (sil3114)
Public bug reported: Running Gutsy / 2.6.22-14-386 Using a PCI SATA controller card with a Silicon Image sil3114 chipset and the sata_sil module, attempting to use the xfs filesystem on a SATA drive attached to it results in an xfs crash and filesystem corruption whenever a write is attempted. lspci for controller: 00:0b.0 Mass storage controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) Subsystem: Silicon Image, Inc. SiI 3114 SATALink Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- ] xfs_btree_check_sblock+0x5b/0xd0 [xfs] [ 3031.116000] [] xfs_inobt_lookup+0x1c9/0x450 [xfs] [ 3031.116000] [] xfs_inobt_lookup+0x1c9/0x450 [xfs] [ 3031.116000] [] kmem_zone_zalloc+0x28/0x60 [xfs] [ 3031.116000] [] xfs_dialloc+0x5cf/0x990 [xfs] [ 3031.116000] [] do_page_fault+0x37c/0x690 [ 3031.116000] [] xfs_ialloc+0x61/0x550 [xfs] [ 3031.116000] [] xfs_dir_ialloc+0x85/0x2d0 [xfs] [ 3031.116000] [] xfs_trans_reserve+0xa4/0x220 [xfs] [ 3031.116000] [] xfs_create+0x398/0x6a0 [xfs] [ 3031.116000] [] xfs_vn_mknod+0x236/0x350 [xfs] [ 3031.12] [] vfs_create+0x108/0x150 [ 3031.12] [] open_namei+0x588/0x5e0 [ 3031.12] [] do_filp_open+0x33/0x60 [ 3031.12] [] do_sys_open+0x4e/0xf0 [ 3031.12] [] filp_close+0x47/0x80 [ 3031.12] [] sys_open+0x1c/0x20 [ 3031.12] [] sysenter_past_esp+0x6b/0xa9 [ 3031.12] [] km_report+0x40/0x80 [ 3031.12] === After the error, if I unmount the filesystem and run xfs_repair on it, I get output like this: xfs_repair /dev/sda2 - creating 2 worker thread(s) Phase 1 - find and verify superblock... - reporting progress in intervals of 15 minutes Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... ir_freecount/free mismatch, inode chunk 0/128, freecount 60 nfree 56 - 05:26:40: scanning filesystem freespace - 8 of 8 allocation groups done - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - 05:26:40: scanning agi unlinked lists - 8 of 8 allocation groups done - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 imap claims a free inode 186 is in use, correcting imap and clearing inode cleared inode 186 imap claims a free inode 188 is in use, correcting imap and clearing inode cleared inode 188 imap claims a free inode 189 is in use, correcting imap and clearing inode cleared inode 189 imap claims a free inode 190 is in use, correcting imap and clearing inode cleared inode 190 - 05:26:40: process known inodes and inode discovery - 64 of 64 inodes done - process newly discovered inodes... - 05:26:40: process newly discovered inodes - 8 of 8 allocation groups done Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - clear lost+found (if it exists) ... - clearing existing "lost+found" inode - deleting existing "lost+found" entry - 05:26:40: setting up duplicate extent list - 8 of 8 allocation groups done - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - 05:26:40: check for inodes claiming duplicate blocks - 64 of 64 inodes done Phase 5 - rebuild AG headers and trees... - 05:26:40: rebuild AG headers and trees - 8 of 8 allocation groups done - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - ensuring existence of lost+found directory - traversing filesystem starting at / ... - 05:26:40: traversing filesystem - 8 of 8 allocation groups done - traversal finished ... - traversing all unattached subtrees ... - traversals finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... - 05:26:40: verify and correct link counts - 64 of 64 inodes done done I have ruled out problems with the hard drive or controller by doing the following: -created ext3 and jfs partitions on same drive, wrote and verified data to those partitions, mounted and unmounted without problems, and the data remained intact. -put SATA disk in external USB enclosure and created and mounted xfs partitions, created and deleted files without any errors. I have upgraded the BIOS on the controller card to the most recent version, but this had no effect. I originally had this problem on Feisty (i386) and so I upgraded to Gutsy to see if t
[Bug 139433] Re: kmail IMAP groupware functionality no longer working
Here is my scenario: I have two machines, both were running Edgy with kmail 1.9.6, and both were configured for groupware folders/imap resources. I have upgraded only one machine to Gutsy, now using kmail 1.9.6 (enterprise 0.20070907.709405). After the upgrade the Gutsy machine has the problem described in this bug. One point of interest, before attempting the workaround here, I compared kmailrc on the Edgy machine and the Gutsy machine, and the [IMAP Resource] sections were exactly the same (except for the account ID's of course): [IMAP Resource] TheIMAPResourceEnabled=true TheIMAPResourceFolderParent=.1869991014.directory/INBOX In Edgy, the groupware folders still work fine, without a "TheIMAPResourceAccount=" line. On the Gutsy machine I tried the workaround; manually adding the TheIMAPResourceAccount= After restarting kontact/kmail, I get the following prompt: "KMail will now create the required groupware folders as subfolders of INBOX; if you do not want this, cancel and the IMAP resource will be disabled" If I say yes/Continue, then the empty Contacts, Cal folders etc. show up in the [cached/disconnected] IMAP acct with the icons indicating they are associated with Contacts, etc. BUT when I try to sync the cached IMAP acct with the server, it fails (Error while uploading folder Could not make the folder on the server...) because the folders already exist on the server (and are full of data) so it cannot create them again, and so it will not sync the existing data either. If I say Cancel to the "Kmail will now create the required groupware folders" prompt, then, as it promised, it disables the groupware functionality and unsets "TheIMAPResourceEnabled=true" in kmailrc. If I manually reset this value in kmailrc and restart kontact, it gives me the same "KMail will now create the required groupware folders" prompt. So the workaround does not work here. -- kmail IMAP groupware functionality no longer working https://bugs.launchpad.net/bugs/139433 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 153239] Re: Kontact: calendar/contacts on cached imap acct no longer works
Yes, it is the same bug, you can mark this a dupe. I will comment in the other bug. -- Kontact: calendar/contacts on cached imap acct no longer works https://bugs.launchpad.net/bugs/153239 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 153239] Kontact: calendar/contacts on cached imap acct no longer works
Public bug reported: Binary package hint: kontact Enable calendar and contacts data on disconnected IMAP acct (aka. IMAP Resource Folders), via KDE Resources and then in Kmail config: Misc -> Groupware in Kontact. Syncronize data with cached IMAP acct. Go to calendar, contacts, they appear blank. Trying to create a new contact/event and sync yields error: "No writable resource was found. Saving will not be possible. Reconfigure KMail first." This was previously configured in Feisty and working fine. Since upgrade to Gutsy, I can no longer access my Calendar/Contact data at all. If I browse the folders from Kmail, I can see the individual VCards for the Calender and Contacts, so all the data is definately there, it just isn't being displayed in the Calendar or Contacts components (nor in kaddressbook for korganizer). I have tried removing the cached imap account and setting up again, removing the groupware settings from Kmail and reconfiguring, and removing and re-adding the KDE imap-resources under Kde Resources in the control panel. Nothing had any effect on the problem. ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- Kontact: calendar/contacts on cached imap acct no longer works https://bugs.launchpad.net/bugs/153239 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153194] kontact navigator toolbar won't stay when moved
Public bug reported: Binary package hint: kontact Using Kontact 1.2.4 (enterprise 0.20070907.709405) on KDE 3.5.8 / Gutsy , the Navigator toolbar resists being positioned in anything but the default placement. By default, the Navigator toolbar is comprised of the special items: "SpacerAction" "ActionList: navigator_actionlist" This populates the Navigator toolbar with six icons, one for each of the Kontact components. When enabled as a horizontal toolbar (along the top), the Navigator toolbar's icons are by default positioned at the right most edge of the screen. The Navigator toolbar's handle appears much further to the left, just after the last icon of the previous toolbar. I would like to place the Navigator toolbar in the left most position at the top, with the other toolbars following just after it on the same line. Kontact will allow me to drag and drop the toolbar into the position described, but upon changing to a different Kontact component, or exiting and restarting Kontact, the Navigator toolbar's position changes. It usually appears on it's own new line, below the component- dependent toolbar(s). I attempted to alter the placement of the Navigator toolbar by deleting the "SpacerAction" from it, the effect of that is that all the icons dissapear from the Navigator toolbar, leaving only its handle. I also attempted to manipulate the the Navigator toolbar's position by manually editing the ~/.kde/share/config/kontactrc file. under the [MainWindow Toolbar navigatorToolBar] heading, but this too was unhelpful. Specifically I tried removing the "NewLine=true" line and altering the Offset value, but these changes did not have a positive effect. Finally I tried removing both the "SpacerAction" and the "ActionList: navigator_actionlist" items from the Navigator toolbar, and manually added the icons for the six Kontact components, all using the "Configure Toolbars" option within Kontact. Even after manually populating the toolbar in this manner, I could not get the Navigator toolbar to stay in the position I placed it. I also tried restoring the Navigator toolbar to its default state, using the "Defaults" button in the "Configure Toolbars" option, but this simply restores the Navigator toolbar to its original right-aligned state. Comparing with a different machine, still running Kontact 1.2.4 on KDE 3.5.6 / Edgy, I am able to place the Navigator toolbar where I desire on that installation, and the toolbar stays put. The only obvious difference is that the Navigator toolbar on that machine has on it only "ActionList: navigator_actionlist", not the "SpacerAction" item. ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- kontact navigator toolbar won't stay when moved https://bugs.launchpad.net/bugs/153194 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73332] Re: Switching users
I have found a workaround for this problem. First, I have verified the following through experimentation: -I cannot get kdm to start on vc/tty8, period. This I do not understand, as I have never seen anything running on tty8 (checked with ps aux). -When logging out a second user, the screen always switches to tty-1, regardless where the first user's X display is running. Given these facts, my workaround is to make the first/original/primary kdm start on tty9. That means that a second user's display will be started on tty10, and I have verified that logging off the second user returns the screen to the first user's display on tty9, as expected. To use this workaround, change the file /etc/kde3/kdm/kdmrc as follows, then restart kdm: old: ServerVTs=-7 new: ServerVTs=-9 -- Switching users https://bugs.launchpad.net/bugs/73332 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 73332] Re: Switching users
I've had the same, or a very simliar problem with Edgy and now with Feisty as well. When logging out the second user (after having done a Switch User), the display doesn't return to the first user's instance of X. It seems that the second user/ X server is always started on vc9. When logging this user out, the display goes to vc8, which has nothing running in it, so I'm looking at a blank screen with a blinking cursor and I have to manually (CTRL-ALT-F7) switch back to vc7. I experience the same problem if I initiate a Remote Login (XDMCP) from the kdm login screen. After logging out the remote connection, I am not returned to the X server on vc7 where kdm is running. -- Switching users https://bugs.launchpad.net/bugs/73332 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 80765] Re: 6.10 Installer refuses due to xfs
Here is the syslog mentioned in the previous comment. ** Attachment added: "syslog" http://librarian.launchpad.net/6148654/syslog -- 6.10 Installer refuses due to xfs https://launchpad.net/bugs/80765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80765] Re: 6.10 Installer refuses due to xfs
I believe I have just run into this same bug while trying to install Kubuntu 6.10. I can reproduce the problem starting with a blank hard drive, and creating three partitions during installation: /boot using ext2 linux-swap / using xfs Using this layout, it will not let me proceed past the screen where you assign mount points to the partitions; complaining [erroneously] that "XFS may not be used on the filesystem containing /boot. Either use a different filesystem for / or create a non-XFS filesystem for /boot". I am attaching syslog and partman from when I tried this configuration and was prevented from continuing with installation. ** Attachment added: "partman" http://librarian.launchpad.net/6148620/partman -- 6.10 Installer refuses due to xfs https://launchpad.net/bugs/80765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
