[Bug 1565975] Re: scanning sometimes impossible with LIDE 210

Today I have tested the latest update for the i386 version of Artful Ardvark. With this version (1.0.27-1~experimental2) the scanner works without excessive noise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1565975] Re: scanning sometimes impossible with LIDE 210

Well, I should have guessed that it is an upstream issue ... Instead of filing an upstream bug, I tested the latest git snapshot from . I compiled the backends and frontends source and tested the newly compiled xscanimage on the i386 machine. With this

[Bug 1565975] Re: scanning sometimes impossible with LIDE 210

Meanwhile I have installed the zesty amd64 version on my desktop. As expected the result was the same as with xenial, i.e. scanning worked but it was rather noisy. As a workaround I installed the trusty packages of xsane, libsane and other dependencies. This version worked for the i386 and amd64

Re: [Bug 1565975] Re: scanning sometimes impossible with LIDE 210

Christopher M. Penalver wrote: > Nils Kassube, to clarify, you tested the amd64 daily on the laptop and > it worked? Christopher, nothing really worked - to clarfy: 1. I don't see a point in trying only the amd64 version - after all i386 is a supported architecture as well, even with ze

Re: [Bug 1565975] Re: scanning sometimes impossible with LIDE 210

On Do, 12. 01.2017 you wrote: > Nils Kassube, to see if this is already resolved in Ubuntu, could you > please test the 64-bit version on your desktop via > http://cdimage.ubuntu.com/daily-live/current/ and advise to the > results? I tried it, but the current amd64 and i

[Bug 1565975] Re: scanning sometimes impossible with LIDE 210

I have two machines with which I want to use the scanner, one of them is the desktop with 64-bit Kubuntu (still 14.04) and the other one is a rather old laptop which is not 64-bit capable (Pentium-M) with 32-bit Kubuntu 16.04. When I discovered the problem on the laptop, I checked it with the

[Bug 1608880] Re: systemd doesnt work with timed fsck, only with counted mount fsck

I can confirm this bug. However /forcefsck seems not to be supported because it isn't mentioned in the man page. When I log in to one of the 16.04 systems, I get this info: *** /dev/sda5 will be checked for errors at next reboot *** But the command "dmesg|grep -i e2fsck" gives this output: [

[Bug 1565975] Re: scanning sometimes impossible with LIDE 210

Today I have taken the xenial sources for sane-backends and xsane and built the libsane and xsane packages with a trusty i386 system. Then I booted the Kubuntu trusty i386 (14.04.3) iso image. First I installed the xsane package from the standard repo and the scanner worked as it should. The I

[Bug 1565975] [NEW] scanning sometimes impossible with LIDE 210

Public bug reported: If I try to scan with xsane or skanlite there is often an error message like "Error during device I/O". If that error message appears, I have to replug the scanner to make it working again. There are several symptom which are not always the same: Sometimes only preview

[Bug 1526931] [NEW] upgrade 14.04->16.04 doesn't replace linux-generic-lts-wily with linux-generic

Public bug reported: I had linux-generic lts-wily (and linux-generic-lts-vivid) installed. After the upgrade with 'do-release-upgrade -d' the old kernel was still in use. I had expected to get the linux-generic package installed for the new xenial kernel. ProblemType: Bug DistroRelease: Ubuntu

[Bug 1306820] [NEW] /etc/update-motd.d/91-release-upgrade failure due to bad quoting

Public bug reported: After todays upgrade trusty is no longer in development according to lsb_release -sd. Therefore the script /etc/update-motd.d/91-release- upgrade fails due to bad quoting. The attached patch fixes the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package:

[Bug 1297936] Re: After upgrade 12.04-14.04 lightdm fails to start

I think the upgrader could check if lightdm was installed before the upgrade. If it wasn't because kdm was in use, then the stale config file could be removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1297936] Re: After upgrade 12.04-14.04 lightdm fails to start

Further experiments showed that it would be better to remove the stale config file /etc/lightdm/lightdm.conf instead of installing the additional package lightdm-gtk-greeter. Then the much nicer qt version of the login screen is in use and the KDE systemsettings can be used to configure the login

[Bug 1297936] [NEW] After upgrade 12.04-14.04 lightdm fails to start

Public bug reported: I upgraded this Kubuntu laptop using the command do-release-upgrade -d from 12.04 to 14.04. After the reboot, the splash screen did not disappear and lightdm didn't start. Running the command start lightdm (as root), I got the error message start: Job failed to start, which

[Bug 1282760] Re: update-motd-fsck-at-reboot claims that partitions will be checked even if check is disabled in fstab

And here is an alternative patch ** Attachment added: This patch changes the message https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1282760/+attachment/3988730/+files/patch2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1282760] [NEW] update-motd-fsck-at-reboot claims that partitions will be checked even if check is disabled in fstab

Public bug reported: When I login remotely I get a message that a partition will be checked at next reboot. This message will appear even after the next reboot because in my /etc/fstab that partition is marked as not to check (last field = 0). Either that message should not appear or it should be

[Bug 1282760] Re: update-motd-fsck-at-reboot claims that partitions will be checked even if check is disabled in fstab

Thanks for the review. With the cut command I want to select the mount point and not the device. The device is known inside the loop from $part but there are several ways to name the device in /etc/fstab (device, UUID, label). It is unknown which version is used for the partition in question. On

[Bug 1264884] Re: 12.04 - 14.04 keeps linux-generic-lts-raring and doesn't install linux-generic

Today I repeated the upgrade on the test-partition and this time the new kernel 3.13 was installed. I only tried it with the lts-raring kernel though. So obviously someone fixed the issue without knowing this bug report. Thanks for taking care of the issue. -- You received this bug notification

[Bug 1264887] Re: After upgrade 12.04 - 14.04 there was no display manager (kdm or lightdm)

Today I repeated the upgrade on the test-partition and I can confirm that the bug is fixed. Thanks for taking care of the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264887 Title: After

[Bug 1264887] Re: After upgrade 12.04 - 14.04 there was no display manager (kdm or lightdm)

Obviously the keydependencies have not been found even though kdm was installed. Or is it required to find both (all) keydependencies? Then the explanation would be that kubuntu-artwork seems not to be available from the kubuntu-backports-ppa and therefore wasn't installed. Would it help if I

[Bug 1264887] Re: After upgrade 12.04 - 14.04 there was no display manager (kdm or lightdm)

Indeed I don't have kubuntu-desktop installed because I removed one (or more) of it's dependencies a long time ago. I think this is not uncommon, though. At the end of the upgrade I didn't let upgrade-manager clean up unused packages, therefore the reason for the removal of kdm seems to be

[Bug 1264887] Re: After upgrade 12.04 - 14.04 there was no display manager (kdm or lightdm)

No, there was no such question. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1264887 Title: After upgrade 12.04 - 14.04 there was no display manager (kdm or lightdm) To manage

[Bug 1264884] [NEW] 12.04 - 14.04 keeps linux-generic-lts-raring and doesn't install linux-generic

Public bug reported: This machine had the kernel linux-generic-lts-raring installed but not linux-generic. After the upgrade to 14.04 with the command update- manager -c -d there was no new kernel installed. The package linux- generic should have been added. I have also tried the upgrade for the

[Bug 1264887] [NEW] After upgrade 12.04 - 14.04 there was no display manager (kdm or lightdm)

Public bug reported: This Kubuntu machine had KDM installed before the upgrade from 12.04 to 14.04. After the upgrade there was no display manager left, i.e. kdm was no longer installed and it wasn't replaced by lightdm like it happened on another machine with a fresh Kubuntu 12.04 system. The

[Bug 1264887] Re: After upgrade 12.04 - 14.04 there was no display manager (kdm or lightdm)

Additional info: The KDE packages of the 12.04 system were from the kubuntu-backports-ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264887 Title: After upgrade 12.04 - 14.04 there was no

[Bug 930993] Re: Lucid - Precise trouble with do-release-upgrade

I forgot the link to the other bug: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/876936 And attached are the log files in /var/log/dist-upgrade. ** Attachment added: dist-upgrade-logs.tgz

[Bug 930993] Re: Lucid - Precise trouble with do-release-upgrade

-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930993 Title: Lucid - Precise trouble with do-release-upgrade To manage notifications about this bug go to:

[Bug 930993] [NEW] Lucid - Precise trouble with do-release-upgrade

Public bug reported: 1. I had installed the package gcj-jdk including dependencies. Removing these packages let the upgrade continue without the error message above. 2. However the upgrade stopped after a few packages were installed with a failure message concerning the package lib32asound2.

[Bug 418560] Re: Unfinished shutdown or reboot

** Attachment added: version.txt http://launchpadlibrarian.net/30813793/version.txt -- Unfinished shutdown or reboot https://bugs.launchpad.net/bugs/418560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 418560] Re: Unfinished shutdown or reboot

** Attachment added: dmesg.txt http://launchpadlibrarian.net/30813777/dmesg.txt -- Unfinished shutdown or reboot https://bugs.launchpad.net/bugs/418560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 418560] [NEW] Unfinished shutdown or reboot

Public bug reported: With the kernel 2.6.31-7 shutdown or reboot stops before the machine is switched off or rebooted. With the previous version (2.6.31-6) or the mainline kernel (2.6.31-020631rc7) the problem doesn't exist. These are the shutdown messages: Stopping K Display Manager: kdm. *

[Bug 418560] Re: Unfinished shutdown or reboot

** Attachment added: lspci-vvnn.txt http://launchpadlibrarian.net/30813781/lspci-vvnn.txt -- Unfinished shutdown or reboot https://bugs.launchpad.net/bugs/418560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 418560] Re: Unfinished shutdown or reboot

** Attachment added: uname-a.txt http://launchpadlibrarian.net/30813796/uname-a.txt -- Unfinished shutdown or reboot https://bugs.launchpad.net/bugs/418560 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 374387] Re: [Karmic] Kernel panic with TV card plugged

This is a patch to fix the kernel oops. To test the patch, download it to your home directory and get the kernel source with the command apt-get source linux-image-$(uname -r) in a terminal. Then goto the new directory linux-2.6.31 and apply the patch: cd linux-2.6.31 patch -p1 ~/af9015.diff

[Bug 206006] Re: Missing display with module lxfb

I have tested the karmic kernel versions 2.6.31-1.14 and mainline 2.6.31-020631rc1gc0d1117-generic. With both kernels the problem doesn't exist any longer. ** Tags removed: needs-upstream-testing -- Missing display with module lxfb https://bugs.launchpad.net/bugs/206006 You received this bug

[Bug 395205] Re: Kernel oops with Cinergy T USB XE

*** This bug is a duplicate of bug 374387 *** https://bugs.launchpad.net/bugs/374387 ** This bug has been marked a duplicate of bug 374387 [Karmic] Kernel panic with TV card plugged -- Kernel oops with Cinergy T USB XE https://bugs.launchpad.net/bugs/395205 You received this bug

[Bug 395205] Re: Kernel oops with Cinergy T USB XE

** Attachment added: dmesg.log http://launchpadlibrarian.net/28660735/dmesg.log -- Kernel oops with Cinergy T USB XE https://bugs.launchpad.net/bugs/395205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 395205] [NEW] Kernel oops with Cinergy T USB XE

Public bug reported: The DVB-T stick Terratec Cinergy T USB XE (USB ID: 0ccd:0069) generates a kernel oops with kernel 2.6.31-1-generic on insertion. This doesn't lock the machine completely but the lsusb command doesn't work after the kernel oops. Therefore I can't report it using ubuntu-bug.

[Bug 395205] Re: Kernel oops with Cinergy T USB XE

** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/28660740/lspci-vvnn.log -- Kernel oops with Cinergy T USB XE https://bugs.launchpad.net/bugs/395205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 395205] Re: Kernel oops with Cinergy T USB XE

** Attachment added: lsusb-v.log http://launchpadlibrarian.net/28660755/lsusb-v.log -- Kernel oops with Cinergy T USB XE https://bugs.launchpad.net/bugs/395205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing

[Bug 395205] Re: Kernel oops with Cinergy T USB XE

** Attachment added: version.log http://launchpadlibrarian.net/28660769/version.log -- Kernel oops with Cinergy T USB XE https://bugs.launchpad.net/bugs/395205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing

[Bug 395205] Re: Kernel oops with Cinergy T USB XE

** Attachment added: uname-a.log http://launchpadlibrarian.net/28660762/uname-a.log -- Kernel oops with Cinergy T USB XE https://bugs.launchpad.net/bugs/395205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing

[Bug 208461] Re: [Hardy] kdesu doesn't work via ssh

Yes, kdesu.distrib kate does work. -- [Hardy] kdesu doesn't work via ssh https://bugs.launchpad.net/bugs/208461 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

[Bug 200589] Re: fwlanusb crashes the system

The module for 2.6.24 doesn't work with 2.6.27 (Intrepid) and it seems you can't even compile the module with the new kernel any longer. You can try if it works with ndiswrapper (or keep the kernel and linux- restricted-modules from Hardy). -- fwlanusb crashes the system

[Bug 203340] Re: Kubuntu Hardy - 2 Error windows after login and no icons on desktop

The situation is unchanged. But here are some more details: To get reproducible results I did a clean install on my machine, so I used the Kubuntu 8.04.1 desktop CD and I did an upgrade of all packages with the default repositories. Then I tested login and the error windows were there. Next I

[Bug 200589] Re: fwlanusb crashes the system

Have just tested the fwlanusb module with packages linux-restricted- modules-2.6.34-21-generic version 2.6.24.14-21.49 and linux- image-2.6.24-12-generic version 2.6.24-21.42. It works for me, i.e. I could connect to my wireless network and the iwconfig cammand works without crash now. Thanks for

[Bug 200589] Re: fwlanusb crashes the system

@exactt: The instructions I gave include the checkinstall command which makes a .deb package and installs it. That's why you should make the package name something useful like fwlanusb. -- fwlanusb crashes the system https://bugs.launchpad.net/bugs/200589 You received this bug notification

[Bug 200589] Re: fwlanusb crashes the system

How to apply the patch: You should uninstall the package linux-restricted-modules because the module from this package would be loaded instead of the newly compiled one. Then enter the commands below in a terminal. Please note: The source code download is 150MB, i.e. several hours for dial-up.

[Bug 200589] Re: fwlanusb crashes the system

Comparing the sources of the fwlanusb and ipw2200 drivers I found a workaround for the bug - see the attached patch. However I don't understand why this works. For me there should not be a difference. ** Attachment added: fwlanusb.dif http://launchpadlibrarian.net/13046036/fwlanusb.dif --

[Bug 208461] [NEW] [Hardy] kdesu doesn't work via ssh

Public bug reported: I login to the Hardy machine with the command ssh -X [EMAIL PROTECTED]. Now I can't start applications with kdesu like kdesu kate. The error message is this: X11 connection rejected because of wrong authentication. kate: cannot connect to X server localhost:10.0 Using gksu

[Bug 206006] Re: Missing display with module lxfb

I can confirm that linking gxfb.ko to lxfb.ko works on my machine as well. BTW: My machine is 500MHz not 600 as mentioned in the original report. -- Missing display with module lxfb https://bugs.launchpad.net/bugs/206006 You received this bug notification because you are a member of Ubuntu

[Bug 206006] [NEW] Missing display with module lxfb

Public bug reported: With the module lxfb loaded, the display of virtual terminals (ALT-F1 ... ALT-F6) only shows a blinking cursor. With this module blacklisted the display works as expected. Hardware: AMD Geode LX800 (600 MHz) with 256 MB ram. ** Affects: ubuntu Importance: Undecided

[Bug 203340] Re: Kubuntu Hardy - 2 Error windows after login and no icons on desktop

Additional information: The problem exists on 2 similar machines with this hardware: CPU: AMD geode LX800 / 500MHz RAM: 256MB Rather slow CF card instead of a hard disk. On one machine I did some more experiments. If I reduce the resolution from 1600x1200 to 800x600 the problem disappears. --

[Bug 203340] [NEW] Kubuntu Hardy - 2 Error windows after login and no icons on desktop

Public bug reported: On a Kubuntu Hardy machine with all updates an error window pop up after login. The window text is Der Prozess für das Protokoll file wurde unerwarted beendet. which translates to Process for protocol file aborted unexpectedly.. After clicking OK a second error window pops up

[Bug 200589] Re: fwlanusb crashes the system

I can confirm this bug. Here the system crashed with the command iwconfig. Attached is part of the output of dmesg from insertion of the Fritz!WLAN USB Stick until crash. ** Attachment added: fwlanusb-oops.txt http://launchpadlibrarian.net/12666920/fwlanusb-oops.txt -- fwlanusb crashes the

[Bug 123615] Konqueror crash when closing tab with keys windows+ctrl+w or windows+ctrl+q

Public bug reported: Open Konqueror, duplicate existing tab (ctrl-shift-d). Then close the new tab with ctrl-w while a windows key is pressed - Konqueror crashes. Alternatively Konqueror crashes with ctrl-q while a windows key is pressed after the confirmation dialog for closing several tabs.