[Desktop-packages] [Bug 2015674] Re: Unread mail notifications do not update
re
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2015674/comments/4
It seems to be true, I removed Thunderbird notifications and the number
in the icon went down.
However that's completely unhelpful given that the number of
notifications has no relevance to anything (as in I can't imagine why
would one want to know that). Not sure if there are other programs where
it could be useful (can't think of any) but for any email, messaging
etc. program it's just misleading. Is this a recent change?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2015674
Title:
Unread mail notifications do not update
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
The Thunderbird icon on the dock shows the count of new mails
correctly, but the icon does not update itself once the emails have
been read. Even restarting the app will not update the icon.
I would expect the notification icon to show zero (new emails) once
the mails have been read.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: thunderbird 1:102.10.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BuildID: 20230405152512
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 12:11:34 2023
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Finnish Language Pack - langpack...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2022-03-22 (382 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric
600
MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-af991e4b-f99c-455f-8b24-2a1ee2160904
bp-e1f0ba3b-5182-4280-9ed6-c76da2160127
UpgradeStatus: Upgraded to lunar on 2023-04-02 (6 days ago)
dmi.bios.date: 06/27/2022
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET72W(1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UH001AMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.41
dmi.modalias:
dmi:bvnLENOVO:bvrR1CET72W(1.41):bd06/27/2022:br1.41:efr1.41:svnLENOVO:pn20UH001AMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UH001AMX
dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2015674/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864778] Re: Intel Drivers Artifacts after Mesa-Dev Update
I don't see this issue anymore, not sure when it was fixed, currently have Ubuntu 20.10: xserver-xorg-video-intel 2:2.99.917+git20200714-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1864778 Title: Intel Drivers Artifacts after Mesa-Dev Update Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1864778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Same here, it stared in Chrome maybe a week ago but now it also affects Chromium. In addition to that opening a new window results in a window that does not update its content, there is just snapshot of whatever was on the screen below the window. Usually maximize/restore fixes it. Ubuntu 20.04 kernel 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Chromium 86.0.4240.75 snap Google Chrome 86.0.4240.75 Intel Corporation Iris Plus Graphics 655, using xorg 'intel' driver, using xorg because Wayland crashes on my system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously Status in chromium-browser package in Ubuntu: Confirmed Bug description: After pressing F11 there's a text box at the top of the screen with the message Press F11 to Exit, etc. Usually this goes away by itself after a few seconds. Now it flashes continuously and won't clear. Pressing F11 again quits full screen mode, but the tab is still flashing in some way and the whole browser is now unstable and not usable. Chrome: Version 86.0.4240.75 (Official Build) (64-bit) System: Ubuntu Studio, Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size
Yes, https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2
fixed the issue for me, thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1889090
Title:
GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
in meta_monitor_manager_xrandr_update_screen_size
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Committed
Bug description:
Reported initially as comments of bug #1887998:
[ Impact ]
Ubuntu session doesn't start with some particular monitor
configurations, as per this fatal assertion:
Jul 27 00:30:33 jojda gnome-shell[15068]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out!
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with
result 'core-dump'.
[ Test case ]
Start ubuntu session, you should be able to log-in and no error
fallback dialog is shown.
[ Regression potential ]
Screen size is not set properly for the session, panning is enabled.
---
https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
does not fix it. Unfortunately I cannot switch to Wayland because it
doesn't start on my system (video card: 00:02.0 VGA compatible
controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).
Symptom is that after waking up from sleep I get white screen of death
that says what the bug description says ("Oh no! Something has gone
wrong. A problem has occurred and the system can't recover. Please log
out and try again.") and I have to click the Log out button at which
points it lets me log in again. Sometime it does the same thing again
right after logging in.
Syslog message are also pretty much the same as from other comments,
here you can see it failing twice, first up while running then right
after re-login.
Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion
'GVC_IS_MIXER_CARD (card)' failed
Jul 27 00:30:32 jojda gnome-shell[4633]: **
Jul 27 00:30:32 jojda gnome-shell[4633]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out!
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled
restart job, restart counter is at 1.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session
(session: ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session:
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature
'x11-randr-fractional-scaling'
Jul 27 00:30:33 jojda gnome-shell[15068]: **
Jul 27 00:30:33 jojda gnome-shell[15068]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out!
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: Failed to start GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session.
Jul 27 00:30:33 jojda
[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it
I have the same problem,
https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 does
not fix it. Unfortunately I cannot switch to Wayland because it doesn't
start on my system (video card: 00:02.0 VGA compatible controller: Intel
Corporation Iris Plus Graphics 655 (rev 01)).
Symptom is that after waking up from sleep I get white screen of death
that says what the bug description says ("Oh no! Something has gone
wrong. A problem has occurred and the system can't recover. Please log
out and try again.") and I have to click the Log out button at which
points it lets me log in again. Sometime it does the same thing again
right after logging in.
Syslog message are also pretty much the same as from other comments,
here you can see it failing twice, first up while running then right
after re-login.
Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion
'GVC_IS_MIXER_CARD (card)' failed
Jul 27 00:30:32 jojda gnome-shell[4633]: **
Jul 27 00:30:32 jojda gnome-shell[4633]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out!
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled restart
job, restart counter is at 1.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session (session:
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session:
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature
'x11-randr-fractional-scaling'
Jul 27 00:30:33 jojda gnome-shell[15068]: **
Jul 27 00:30:33 jojda gnome-shell[15068]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out!
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: Failed to start GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session
(session: ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: gnome-session-x11@ubuntu.target: Job
gnome-session-x11@ubuntu.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-session-x11.target: Job
gnome-session-x11.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.target: Job
gnome-shell-x11.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled restart
job, restart counter is at 2.
Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1887998
Title:
Update to 3.36.4 and SRU it
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Committed
Bug description:
[ Impact ]
That's the current GNOME stable update, including some fixes and translation
updates
https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4
[ Test case ]
The update is part of GNOME stable updates
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
GNOME Shell and its components should continue working
[ Regression potential ]
There have been fixes in X11 screencasting and touch-interaction, so
ensure there are no problems with those.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1864778] Re: Intel Drivers Artifacts after Mesa-Dev Update
Just upgraded to Ubuntu 20.4, seeing same symptoms, screen artifacts after X startup and some fonts corruption. Font problems are in some applications/windows only, e.g. Chrome window, gvim, terminal are all fine (so far). However Unity taskbar and System tray usually have broken fonts (some characters). Video card: 00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics 655 (rev 01) It happens with or without custom config (needed to stop video tearing): Section "Device" Identifier "Intel Graphics" Driver "Intel" Option "AccelMethod" "sna" Option "TearFree" "true" Option "TripleBuffer" "true" Option "MigrationHeuristic" "greedy" Option "Tiling" "true" Option "Pageflip" "true" Option "ExaNoComposite" "false" Option "Tiling" "true" Option "Pageflip" "true" EndSection Also tried Wayland but it's a no go because it freezes right after I enter password in gdm3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1864778 Title: Intel Drivers Artifacts after Mesa-Dev Update Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 20.0.0-1ubuntu1 mesa I get serious artifacts on startup when using the intel driver instead of modesetting. These artifacts go away when I enable Option AccelMethod "uxa" but persist if the default, "sna" or the other modes are used "none", "off", "blt". These pixels appear throughout the experience of using Ubuntu and generate in sporadic places. The font also looks completely broken. I've never had this issue before with the Intel drivers. I have Skylake HD 530. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1864778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
Is this duplicate of https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/1247371? I have the same problem with Fujitsu S1300 scanner on Ubuntu 14.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in Simple Scan: New Status in “sane-backends” package in Ubuntu: Confirmed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1184699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
