Lucas Partridge, at your earliest convenience, could you please test the
latest upstream kernel available from the very top line at the top of
the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
(the release names are irrelevant for testing, and please do not test
the daily folder)? Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.
If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.
If the latest kernel did not allow you to test to the issue (ex. you couldn't
boot into the OS) please make a comment in your report about this, and continue
to test the next most recent kernel version until you can test to the issue.
Once you've tested the upstream kernel, please comment on which kernel version
specifically you tested. If this issue is fixed in the mainline kernel, please
add the following tags by clicking on the yellow circle with a black pencil
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ
Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.
If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ
Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.
Once testing of the latest upstream kernel is complete, please mark this
report's Status as Confirmed. Please let us know your results.
Thank you for your understanding.
** Tags added: latest-bios-1.3
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1529232
Title:
Scanner not detected over wifi since after 3.13.0-68
Status in linux package in Ubuntu:
Incomplete
Bug description:
Please see http://ubuntuforums.org/showthread.php?t=2306464 for
details. I'm running 64-bit 14.04 LTS ubuntu.
When I boot my PC into 3.13.0-68-generic (via the 'ubuntu advanced'
menu item in grub) I can detect my scanner over wifi using scangearmp.
However since 3.13.0-70-generic I have not been able to detect my
scanner over wifi. My current kernel is 3.13.0-74-generic. Therefore
I suspect a regression has occurred between 3.13.0-68-generic and
3.13.0-70-generic:
Scanner *is* detected by scangearmp over wifi and it scans documents as
expected in this version:
uname -a
Linux zorro 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
But scanner is *not* detected by scangearmp in this version or later:
Linux zorro 3.13.0-70-generic #113-Ubuntu SMP Mon Nov 16 18:34:13 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Note that this happened before some time ago. i.e., The scanner was
detected over wifi, then not, then it was again some time later. Then
this latest break occurred again. I suspect successive updates are
fixing or breaking the detection accordingly.
$ dpkg -l | grep scangear
ii scangearmp-common 2.20-1
amd64 ScanGear MP for Linux.
ii scangearmp-mg7100series 2.20-1
amd64 ScanGear MP for Linux.
Device is Canon Pixma MG7150 (combined printer, scanner, copier). Note
the printer works fine over wifi; only the scanner is affected.
I can see from the changelog at
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.13.0-74.118/changelog
that many changes went into 3.13.0-69.112 but it's not obvious to me which of
these might have caused the regression.
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: lucas 1604 F.... pulseaudio
/dev/snd/controlC2: lucas 1604 F.... pulseaudio
/dev/snd/controlC0: lucas 1604 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=0140e677-b732-4571-a80a-fc5d7c00359c
InstallationDate: Installed on 2014-12-05 (387 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7528
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic
root=UUID=941f5e44-f02e-42f2-ac78-5f6b4b9e98e9 ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
RelatedPackageVersions:
linux-restricted-modules-3.13.0-74-generic N/A
linux-backports-modules-3.13.0-74-generic N/A
linux-firmware 1.127.19
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: trusty
Uname: Linux 3.13.0-74-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/19/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G31M3-F(MS-7528)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd06/19/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7528:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-F(MS-7528):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7528
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
