[Bug 119253] Re: crash on 2.6.20-16.28
This bug doesn't seem to appear in 2.6.20-16.29, so I'm changing to Fix Released. ** Changed in: linux-source-2.6.20 (Ubuntu) Status: New = Fix Released -- crash on 2.6.20-16.28 https://bugs.launchpad.net/bugs/119253 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 128074] strange font behaviour - connected letters
Public bug reported: Binary package hint: evince Hello, in a particular PDF I have, the letters seem strangely connected, and some appear as symbols. The same file appears nicely in xpdf and adobe reader. I'm including a screenshot. How can I provide better information to get it fixed? ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 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 128074] Re: strange font behaviour - connected letters
I forgot to mention I'm using Feisty. Here's the screenshot. ** Attachment added: evince-feisty.png http://launchpadlibrarian.net/8561960/evince-feisty.png -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 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 128074] Re: strange font behaviour - connected letters
And here's the original file. evince prints it ok, FWIW (except for bug #120861, but that can be worked around). ** Attachment added: Pybus_et_al_2000_Genetics.pdf http://launchpadlibrarian.net/8561964/Pybus_et_al_2000_Genetics.pdf -- strange font behaviour - connected letters https://bugs.launchpad.net/bugs/128074 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 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
Just to add that after purging and recreating all printer configurations, I am now able to print in bw with evince, provided everytime I open it, I change from 'Normal Color', to 'Grayscale'. Still annoying, but at least it works. -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 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 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartridge completely
** Summary changed: - printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely + printout mode always starts with Normal (Color cartrigde) only, skipping black cartridge completely -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartridge completely https://bugs.launchpad.net/bugs/120861 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 19057] Re: Problem with dead keys, cannot write some accentuated characters with KDE apps
I had this with Edgy, but I just tested on Feisty and it seems fixed in KDE 3.5.7. I changed my locale to ISO-8859-1 (pt_BR), logged into KDE and tried dead keys accents with konsole, kmail and konqueror. For all I know, this is fixed now. I am setting the report to Fix Released, since this is not the official version. ** Changed in: kdebase (Ubuntu) Status: Confirmed = Fix Released -- Problem with dead keys, cannot write some accentuated characters with KDE apps https://bugs.launchpad.net/bugs/19057 You received this bug notification because you are a member of Kubuntu Team, which is a direct subscriber. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
Sebastien, If there is a fix, can I get/apply the fix or workaround still in feisty? -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 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 120861] printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
Public bug reported: Binary package hint: evince This doesn't happen to acroread or kpdf. Other gtk apps that use gnome print system (openoffice and firefox) also don't suffer, so I am reporting on evince only. Everytime I start evince, the Advanced tab in Print option in General menu is reconfigured so that it only uses the color cartridge. Even if I change Printout Mode and/or Resolution, Quality, Ink Type and Media Type to use the black cartridge, evince seems to ignore this and still uses only the color cartridge. This is especially bad for me since I currently only have a black cartridge, so paper comes out completely white, making evince useless for printing PDFs. This happens on two Feisty computers (desktop and laptop) I have here. Not sure if it's relevant, but the printer is a HP OfficeJet 4255, using hpijs (recommended) - HPLIP 1.7.3 OfficeJet 4200 driver. ProblemType: Bug Architecture: i386 Date: Sun Jun 17 12:57:03 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evince Package: evince 0.8.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: evince ProcCwd: /home/philsf ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:pt_PT SourcePackage: evince Uname: Linux peralta 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux ** Affects: evince (Ubuntu) Importance: Undecided Status: Unconfirmed -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 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 120861] Re: printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/8107923/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/8107924/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/8107925/ProcStatus.txt -- printout mode always starts with Normal (Color cartrigde) only, skipping black cartrigde completely https://bugs.launchpad.net/bugs/120861 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 119253] crash on 2.6.20-16.28
Public bug reported: Binary package hint: linux-image-2.6.20-16-generic I experienced some strange behaviours, with X applications randomly crashing, and not being able to kill them (firefox and amarok for instance). Restarting X cleaned the zombie apps as expected, but then I noticed strange kernel messages in the console. After starting a new gnome session, I couldn't also start some applications, like amsn for instance. Using Feisty on a Pentium D. RAM is fine, as per memtest. I will attach what appears in kern.log, which recommends to reboot. I did, and everythig is fine since then. I don't know what triggered the crash. PS: I am only attaching this to the security team in case a regression is in order. Sorry if this is inappropriate. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed ** Visibility changed to: Public -- crash on 2.6.20-16.28 https://bugs.launchpad.net/bugs/119253 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 119253] Re: crash on 2.6.20-16.28
** Attachment added: backtrace-kern.log http://launchpadlibrarian.net/8024343/backtrace-kern.log -- crash on 2.6.20-16.28 https://bugs.launchpad.net/bugs/119253 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 104652] Re: sysvinit prevents system from an upgrade
I also thank, as was I just having problems *after* ugrading to feisty, and having update-manager always complain about a broken upgrade. I always suggested to do a partial upgrade that always failed (complaining about lack of space in /boot partition). All this was safe to ignore until patience ran out. I narrowed down the problem to ubuntu-minimal depending on sysvinit and ubuntu-desktop depending on upstart, which conflicts and replaces it. I thought having dapper repos shouldn't break anything, because meta- packages should have indepentent dependencies, but I guess I'm proven wrong. It's still strange, but with the tip from this bug report, the updates now are smooth. Thanks again. -- sysvinit prevents system from an upgrade https://bugs.launchpad.net/bugs/104652 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 60732] Re: Package broken
** Changed in: kde-i18n-ptbr (Ubuntu) Status: Confirmed = Fix Released -- Package broken https://bugs.launchpad.net/bugs/60732 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 66313] Re: Calendar does not synch with palm device
Can anyone confirm that kpilot works in feisty final? I may still be experiencing these crashes, not sure exactly why. -- Calendar does not synch with palm device https://bugs.launchpad.net/bugs/66313 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 82519] Re: kdar: slice size too large for DVD-R's
I created a 3.5 GB dar encrypted (blowfish) with dar without problems. Burned it with K3b, also without problems. Maybe it IS a kdar issue, after all. Can anyone confirm this upstream? Also: kdar crashes when handling this file, e.g., when checking for diffs. dar does not. -- kdar: slice size too large for DVD-R's https://bugs.launchpad.net/bugs/82519 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 43946] Re: Issues with deadkeys in the console
Just for info: doesn't occur in my Edgy (pt_BR locale, abnt2 brazillian keyboard). console-data 2:1.0-2ubuntu5 console-setup 1.7ubuntu19 console-tools 1:0.2.3dbs-62ubuntu10 console-common 0.7.59ubuntu1 I however can't get my /? key to work at all in console (no problems in X). -- Issues with deadkeys in the console https://launchpad.net/bugs/43946 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43946] Re: Issues with deadkeys in the console
Tried including the following line to /usr/share/keymaps/i386/qwerty/br-abnt2.kmap.gz , which in turn came from br-latin1.kmap.gz, and changed the keycode from 53 to 211 as it was the keycode reported by xev. -- keycode 211 = slashquestion degree questiondown -- -- Issues with deadkeys in the console https://launchpad.net/bugs/43946 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61166] Re: br-abnt2.kmp is missing some keycodes
Confirmed, Edgy Eft here. ** Changed in: console-data (Ubuntu) Status: Unconfirmed = Confirmed -- br-abnt2.kmp is missing some keycodes https://launchpad.net/bugs/61166 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43946] Re: Issues with deadkeys in the console
My issue with slash/question keycodes is mentioned/resolved in bug #61166. -- Issues with deadkeys in the console https://launchpad.net/bugs/43946 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63408] Re: failing to find fonts: dexconf writes bogus FontPaths
Why not just make /usr/share/X11/fonts/ a symlink to /usr/share/fonts/X11/? It would make it simpler so that all fonts would end up in the big fonts directory. -- failing to find fonts: dexconf writes bogus FontPaths https://launchpad.net/bugs/63408 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
