[Desktop-packages] [Bug 1989152] Re: wakeup file is ignored
** Package changed: ubuntu => gnome-power-manager (Ubuntu) ** Summary changed: - wakeup file is ignored + suspend wakeup file is ignored ** Description changed: - Writing "disabled" to wakeup file is not working: + Writing "disabled" to wakeup file is ignored after suspend. sudo sh -c "echo 'disabled' > /sys/bus/usb/devices/[bus- port.port]/power/wakeup" This did work with Ubuntu 20.04, but is not working with 22.04. I have verified [bus-port.port] above is correct on my system for my mouse using lsusb and lsusb -t. My mouse still wakes the computer. Furthermore, the wakeup file persists after a reboot without repeating the above command in my .bashrc file. ** Summary changed: - suspend wakeup file is ignored + 22.04 Suspend wakeup file is ignored ** Description changed: - Writing "disabled" to wakeup file is ignored after suspend. + 22.04 Writing "disabled" to wakeup file is ignored after suspend. sudo sh -c "echo 'disabled' > /sys/bus/usb/devices/[bus- port.port]/power/wakeup" This did work with Ubuntu 20.04, but is not working with 22.04. I have verified [bus-port.port] above is correct on my system for my mouse using lsusb and lsusb -t. My mouse still wakes the computer. Furthermore, the wakeup file persists after a reboot without repeating the above command in my .bashrc file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1989152 Title: 22.04 Suspend wakeup file is ignored Status in gnome-power-manager package in Ubuntu: New Bug description: 22.04 Writing "disabled" to wakeup file is ignored after suspend. sudo sh -c "echo 'disabled' > /sys/bus/usb/devices/[bus- port.port]/power/wakeup" This did work with Ubuntu 20.04, but is not working with 22.04. I have verified [bus-port.port] above is correct on my system for my mouse using lsusb and lsusb -t. My mouse still wakes the computer. Furthermore, the wakeup file persists after a reboot without repeating the above command in my .bashrc file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1989152/+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 1743247] Re: B2 Python APIs are missing
This bug report was originally against the PPA package (0.7.16-0ubuntu1ppa1347~ubuntu16.04.1) and not those included in Ubuntu's repositories. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in Duplicity: Won't Fix Status in duplicity package in Ubuntu: Confirmed Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1743247/+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 1743247] Re: B2 Python APIs are missing
If pip is the recommended installation method, and apt packages aren't complete or tested, should https://launchpad.net/~duplicity- team/+archive/ubuntu/ppa be marked as deprecated? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in Duplicity: Won't Fix Status in duplicity package in Ubuntu: Confirmed Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1743247/+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 1311828] Re: Xorg crashed with SIGABRT
** Also affects: xorg-server (Linux From Scratch) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1311828 Title: Xorg crashed with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Status in xorg-server package in Linux From Scratch: New Bug description: TEST CASE: Note: reproduced on a desktop with a touch screen 1. Open gallery-app preloaded with picture 2. Open a picture 3 Switch between picture with touch gestures ACTUAL RESULT After switching between pictures back and forth, this crash occurs This crash also occurs with ubuntu-calculator-app ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Wed Apr 23 20:37:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0629] InstallationDate: Installed on 2014-04-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 3138 ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=5cbfbe7d-ae82-4bcf-aa3c-9b23c133ee5b ro quiet splash Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () ?? () ?? () from /usr/lib/xorg/modules/input/evdev_drv.so ?? () ?? () Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/30/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FC0K2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd08/30/2013:svnDellInc.:pnInspiron3138:pvr:rvnDellInc.:rn0FC0K2:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 3138 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 23 20:38:22 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16476 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1311828/+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 1743247] Re: B2 Python APIs are missing
Thanks. The main advantage of sticking with apt is unattended-upgrades makes it easy to be sure security updates are applied automatically. I’m not familiar with a similar solution for pip, and it sounds like “upgrade everything” isn’t that straightforward (according to https://github.com/pypa/pip/issues/3819). Any idea why the 0.7.14 release works? Was there a refactoring that extracted out the B2 code? Perhaps a warning when upgrading about any removed libraries would help future upgraders. ** Bug watch added: github.com/pypa/pip/issues #3819 https://github.com/pypa/pip/issues/3819 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in Duplicity: In Progress Status in duplicity package in Ubuntu: New Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1743247/+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 1743247] [NEW] B2 Python APIs are missing
Public bug reported: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Description changed: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 - which works fine on 16.04, which makes me think this regression was - added in 0.7.15 or 0.7.16. + which works fine on 16.04, which makes me think this regression was in + 0.7.15 or 0.7.16. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in duplicity package in Ubuntu: New Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1743247/+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 1531683] Re: package libtidy-0.99-0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libtidy.so', which is also in package tidy 5.0.0
Using Ubuntu 16.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tidy in Ubuntu. https://bugs.launchpad.net/bugs/1531683 Title: package libtidy-0.99-0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libtidy.so', which is also in package tidy 5.0.0 Status in tidy package in Ubuntu: Confirmed Bug description: I manually updated to HTML5 tidy yesterday the sudo apt-get update just gave an installation error that's all ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libtidy-0.99-0 (not installed) ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: libtidy-0.99-0: Install tidy: Install libtidy-0.99-0: Configure tidy: Configure Architecture: amd64 Date: Wed Jan 6 20:02:12 2016 DpkgTerminalLog: Preparing to unpack .../libtidy-0.99-0_20091223cvs-1.2ubuntu1.1_amd64.deb ... Unpacking libtidy-0.99-0 (20091223cvs-1.2ubuntu1.1) ... DuplicateSignature: package:libtidy-0.99-0:(not installed):trying to overwrite '/usr/lib/libtidy.so', which is also in package tidy 5.0.0 ErrorMessage: trying to overwrite '/usr/lib/libtidy.so', which is also in package tidy 5.0.0 InstallationDate: Installed on 2015-12-30 (8 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: tidy Title: package libtidy-0.99-0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libtidy.so', which is also in package tidy 5.0.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tidy/+bug/1531683/+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 1345058] [NEW] desktop background image scrambled during login
Public bug reported: Scrambled background image while login in. After 10 seconds normal background image appears. Included screenshot of problem. Problem is not present with nvidia proprietary driver. Description:Ubuntu 14.04 LTS Release:14.04 xserver-xorg-video-nouveau: Installed: 1:1.0.10-1ubuntu2 Candidate: 1:1.0.10-1ubuntu2 Version table: *** 1:1.0.10-1ubuntu2 0 500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jul 19 20:52:37 2014 InstallationDate: Installed on 2014-07-05 (13 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: desktop_image_after_login.png https://bugs.launchpad.net/bugs/1345058/+attachment/4157200/+files/desktop_image_after_login.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1345058 Title: desktop background image scrambled during login Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Scrambled background image while login in. After 10 seconds normal background image appears. Included screenshot of problem. Problem is not present with nvidia proprietary driver. Description: Ubuntu 14.04 LTS Release: 14.04 xserver-xorg-video-nouveau: Installed: 1:1.0.10-1ubuntu2 Candidate: 1:1.0.10-1ubuntu2 Version table: *** 1:1.0.10-1ubuntu2 0 500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jul 19 20:52:37 2014 InstallationDate: Installed on 2014-07-05 (13 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1345058/+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 418242] Re: Incorrect call to output plugins (with persistent error message) on copy
Same problem with Inkscape-trunk and inkscape 0.48.4 on ubuntu 12.04LTS running Matlab R2013b. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/418242 Title: Incorrect call to output plugins (with persistent error message) on copy Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Debian: Confirmed Status in Gentoo Linux: Unknown Bug description: UPDATE: After further investigation it turned out to be a problem related to the copy operation, in combination with a totally unrelated running Java program (FreeRapid). Reading some followups and other bug reports, it seems to be caused by the new clipboard management system (introduced as a fix for the bug #170185), as reported in bug #421597 So far these applications are known to randomly trigger an input/output extension (on linux): - FreeRapid Downloader - jDownloader - xfce4-clipman-plugin 1.1.3 - Netbeans - xfce4-settings-helper (Xfce 4.8) - The original report was this: I'm getting this error when I try to edit a text object created previously with a font that's not available in this system. It looks like Inkscape has problems to resolve the font substitution and displays the error message in a popup window that keeps appearing again and again, leaving no other remedy than closing inkscape and reopening it. The error message is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/418242/+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 1163107] Re: Wacom calibration results are off (wrong area)
There is a bug in gnome's bugzilla now. https://bugzilla.gnome.org/show_bug.cgi?id=703783 Apologies if I am entering this incorrectly. ** Bug watch added: GNOME Bug Tracker #703783 https://bugzilla.gnome.org/show_bug.cgi?id=703783 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1163107 Title: Wacom calibration results are off (wrong area) Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163107/+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 1157318] Re: Login error in CUPS when adding a printer (or other admin procedure)
I have 1.6.2-1ubuntu5. I see the changelog: cups (1.6.2-1ubuntu5) raring; urgency=low * debian/patches/usb-backend-more-quirk-rules.patch: Added quirk rule for the QinHeng CH340S USB-Parallel adapter (LP: #1000253). -- Till Kamppeter till.kamppe...@gmail.com Mon, 15 Apr 2013 15:13:01 +0200 cups (1.6.2-1ubuntu4) raring; urgency=low * debian/local/apparmor-profile: Allow audit_write capability. (LP: #1157318). I assume I have the fix but I still see app armor denied in /var/log/kern.log Let me know your thoughts. I am trying proposed package 7 for. Regards Matt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1157318 Title: Login error in CUPS when adding a printer (or other admin procedure) Status in “cups” package in Ubuntu: Fix Released Bug description: Using Raring (13.04): When you go to http://localhost:631 to do admin tasks in cups, and enter your login details, the system keep asking the user/password in a loop. In the cups log: E [19/Mar/2013:18:20:10 +0100] [Client 17] pam_authenticate() returned 4 (System error) E [19/Mar/2013:18:20:42 +0100] [Client 16] pam_authenticate() returned 4 (System error) E [19/Mar/2013:18:20:49 +0100] [Client 15] pam_authenticate() returned 4 (System error) In the auth log no info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1157318/+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 1157318] Re: Login error in CUPS when adding a printer (or other admin procedure)
package 1.6.2-1ubuntu7 package also fails for me. I disable apparmor_parser -R usr.sbin.cupsd and I can now log in ok. Comparing my profile settings with installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1157318 Title: Login error in CUPS when adding a printer (or other admin procedure) Status in “cups” package in Ubuntu: Fix Released Bug description: Using Raring (13.04): When you go to http://localhost:631 to do admin tasks in cups, and enter your login details, the system keep asking the user/password in a loop. In the cups log: E [19/Mar/2013:18:20:10 +0100] [Client 17] pam_authenticate() returned 4 (System error) E [19/Mar/2013:18:20:42 +0100] [Client 16] pam_authenticate() returned 4 (System error) E [19/Mar/2013:18:20:49 +0100] [Client 15] pam_authenticate() returned 4 (System error) In the auth log no info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1157318/+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 1163107] Re: Wacom calibration results are off (wrong area)
Not your fault for missing it. I had assumed I made a change on my end when installing the gnome source that got things working. I will try this on a live image to see if it is somehow based on the values in conf. Could be that the issue still exists in the latest source, actually. Probably won't get a chance to do this till later this week, though. Any chance you have example bad values handy? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1163107 Title: Wacom calibration results are off (wrong area) Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163107/+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 1163107] Re: Wacom calibration results are off (wrong area)
Just checking to see if the calibration is still off for anyone else. As noted, it seems to be working as desired for me, now. My hunch is that something has changed the default list of my devices such that the Touch device is the middle one. The end device is now my Eraser device. As such, even if it is picked for calibration, I'll get the correct data. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1163107 Title: Wacom calibration results are off (wrong area) Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163107/+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 1163107] Re: Wacom calibration results are off (wrong area)
One oddball update on this. The last few times I have tried the calibration in the settings menu, it has actually worked correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1163107 Title: Wacom calibration results are off (wrong area) Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163107/+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 1163107] Re: Wacom calibration results are off (wrong area)
So, I put in more time than I'd care to admit getting the gnome source compiling so I could test this. It appears the latest version does not have this issue, though I could not find a bug directly related to this. I sent an email to the gnomecc-list asking if this was a known issue, if there was a way I could verify it was an issue with the old version, and if there was a bug this was directly related to. Will update here when I hear back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1163107 Title: Wacom calibration results are off (wrong area) Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163107/+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 1163107] Re: Wacom calibration results are off (wrong area)
I am going to be away from a net connection most of today. A quick search upstream does not show anything regarding this. Will get the required accounts created and bugs enterred when I get a chance this evening. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1163107 Title: Wacom calibration results are off (wrong area) Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163107/+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 1163107] Re: Wacom calibration results are off (wrong area)
Looks like if you want to save the settings stored by the calibration tool, you simply need to use the dconf tool and search for wacom. One of the items directly under wacom has the key of area. Simply set that to what you would get with: xsetwacom --get ... area I am more than interested in trying to dig into the code. I believe I have it checked out correctly, though I am not clear on the process for testing my changes. Has this already been solved by anyone else? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1163107 Title: Wacom calibration results are off (wrong area) Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: When I try to calibrate the touchscreen on my laptop (HP EliteBook 2760p, Wacom Serial Tablet WACf004) the result gets worse and worse with every calibration. The area on which the touchscreen is effective becomes smaller every time to the point where it is completely unusable. This can be verified with xsetwacom --get 15 area, right now this gives me -9978 -6651 6336 -4878. I can reset this by manually setting a new area, e.g. xsetwacom --set 15 area 0 0 25000 16000 However, xsetwacom only works for the current session, after a reboot all information is lost and the calibration is off again. What should happen: the area for the touchscreen is improved with calibrating What happens instead: the area gets smaller for every calibration I'd be happy to contribute a bit in fixing this bug, but my knowledge is limited. Meanwhile, I'd appreciate a workaround: how can I reset the area used for the touchscreen to the default? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Tue Apr 2 14:19:57 2013 InstallationDate: Installed on 2013-03-20 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130319) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.04.01-0ubuntu1 indicator-datetime 12.10.3daily13.03.07-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1163107/+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
