[Desktop-packages] [Bug 1295207] Re: Migrate to farsight 0.2* / gstreamer 1.0
** Bug watch added: Debian Bug tracker #731122 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731122 ** Also affects: pidgin (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731122 Importance: Unknown Status: Unknown ** Bug watch added: Pidgin Trac #15299 http://developer.pidgin.im/ticket/15299 ** Also affects: pidgin via http://developer.pidgin.im/ticket/15299 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1295207 Title: Migrate to farsight 0.2* / gstreamer 1.0 Status in Pidgin: Unknown Status in pidgin package in Ubuntu: Confirmed Status in pidgin package in Debian: Unknown Status in pidgin package in Fedora: Unknown Bug description: 1) Ubuntu 14.04 2) 1:2.10.9-0ubuntu2 3) I expect it to depend against the latest farsight/gstreamer 1.0 4) Instead, it's one of the reasons we still have gstreamer0.10 on the trusty cd, through libpurple. It seems upstream already supports building against farstream-0.2 and gstreamer1.0, see: https://developer.pidgin.im/wiki/Dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin/+bug/1295207/+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 1295207] Re: Migrate to farsight 0.2* / gstreamer 1.0
** Changed in: pidgin (Debian) Status: Unknown = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1295207 Title: Migrate to farsight 0.2* / gstreamer 1.0 Status in Pidgin: Unknown Status in pidgin package in Ubuntu: Confirmed Status in pidgin package in Debian: Confirmed Status in pidgin package in Fedora: Unknown Bug description: 1) Ubuntu 14.04 2) 1:2.10.9-0ubuntu2 3) I expect it to depend against the latest farsight/gstreamer 1.0 4) Instead, it's one of the reasons we still have gstreamer0.10 on the trusty cd, through libpurple. It seems upstream already supports building against farstream-0.2 and gstreamer1.0, see: https://developer.pidgin.im/wiki/Dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin/+bug/1295207/+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 1430358] Re: ubuntu crash on start
** Information type changed from Private to Public -- 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/1430358 Title: ubuntu crash on start Status in xorg-server package in Ubuntu: New Bug description: lubuntu start with black screen. Now I can't log in to Lubuntu enviroment. When i try to log in massage is showede: Starting version 219 [ OK ] Started Light Display Manager. and the loging screen si showed again. In past booting up is slow but i was able to log in. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432681 ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.16.2.901-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu2 Architecture: i386 Date: Tue Mar 10 12:41:44 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-03-16 (724 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server UpgradeStatus: Upgraded to vivid on 2015-02-27 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1430358/+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 1418357] Re: gnome-system-log auto-scrolls away from entry being viewed
@Ubfan: Unfortunately, Gnome seems to have removed this option from the gnome-system-log that comes with 15.04 (there's a surprise!). I think it was already gone by 14.10, but I don't have a 14.10 installation around to check anymore. The only menu I can see is on the cog (right hand side of the title bar) and it has only Open, Close, Copy, Select All, Zoom In, Zoom Out, Normal Size, and Filters. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-log in Ubuntu. https://bugs.launchpad.net/bugs/1418357 Title: gnome-system-log auto-scrolls away from entry being viewed Status in One Hundred Papercuts: Confirmed Status in gnome-system-log package in Ubuntu: Confirmed Bug description: If you run gnome-system-log (the gnome app that hasn't been modified to fit in with the Unity theme) and scroll to look at a particular line, ie so you are not on the last line of the log, when the system adds another log entry gnome-system-log automatically scrolls to this new entry, losing your previous position. This makes it very difficult to use. I would expect it to follow its previous behaviour, which is that if you are on the last line of the log, it auto-scrolls to show new entries, but if you are not on the last line, it never auto-scrolls. It would even be preferable if it never auto-scrolled or if there were an option to turn auto-scrolling on and off. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-system-log 3.9.90-2 Uname: Linux 3.19.0-031900rc7-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 5 14:19:41 2015 InstallationDate: Installed on 2015-01-02 (34 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141220) SourcePackage: gnome-system-log UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1418357/+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 1308954] Re: AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume from suspend with fglrx-updates
@job (jeppekdahl) Hi, from the launchpad page for fglrx-installer-updates [1] the version number is still 2:13.350.1 Could you explain why you mark it as Fix-Released in Trusty? I will revert it to the status in comment #9 [1] https://launchpad.net/ubuntu/+source/fglrx-installer-updates ** Changed in: fglrx-installer-updates (Ubuntu) Assignee: job (jeppekdahl) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer-updates (Ubuntu Trusty) Status: Fix Released = In Progress ** Changed in: hwe-next/trusty Status: Fix Released = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1308954 Title: AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume from suspend with fglrx-updates Status in HWE Next Project: Triaged Status in HWE Next trusty series: In Progress Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer-updates source package in Trusty: In Progress Bug description: SRU Justification [impact] this bug is blocking us to pass certification on OEM hardware. [test case] 1. Install 14.04 and fglrx-updates driver 2. Suspend the machine 3. Wake it up Expected result: * Everything should work fine before and after S3 [regression potential] - CID: 201305-13624 This system would freeze after resume from suspend with fglrx-updates on Trusty. Steps: 1. Install 14.04, and fglrx-updates driver 2. Suspend 3. Wake it up Expected results: * Everything works fine before / after S3 Actual results: * After S3, I can see the login screen, caps lock LED and touchpad still responsive, but I can't login. Few seconds later, system froze, error message could be found in syslog kernel: [ 599.576267] 3[fglrx:firegl_pplib_notify_event] *ERROR* PPLIB: PPLib Notify Event failed! kernel: [ 599.576268] 3[fglrx:firegl_pplib_notify_event] *ERROR* ulEventType = 0002, ulEventData = ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx-updates 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .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 CurrentDesktop: Unity Date: Thu Apr 17 16:42:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-23-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-10 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=ef6ba3b5-e12b-4029-9d6b-cb1753a88ce5 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer-updates UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.fglrx-installer: fglrx-installer N/A 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:
[Desktop-packages] [Bug 1433897] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1431041 *** https://bugs.launchpad.net/bugs/1431041 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1431041, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1433897/+attachment/4349608/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1433897/+attachment/4349611/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1433897/+attachment/4349619/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1433897/+attachment/4349621/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1433897/+attachment/4349622/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1433897/+attachment/4349623/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1433897/+attachment/4349624/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1431041 cups-browsed crashed with SIGSEGV in timeout_free() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1433897 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() Status in cups-filters package in Ubuntu: New Bug description: Crash when system boot ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CupsErrorLog: Date: Wed Mar 18 01:17:36 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2013-05-08 (679 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130508) Lpstat: device for Canon-MG2200-series: usb://Canon/MG2200%20series?serial=A1279Finterface=1 MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Papersize: a4 PpdFiles: Canon-MG2200-series: Canon MG2200 series - CUPS+Gutenprint v5.2.10 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=753d4972-e208-4a9e-8bda-109159ea1925 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fde3839115a:movl $0x1,0xa8(%rax) PC (0x7fde3839115a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-DS2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1433897/+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 1308954] Re: AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume from suspend with fglrx-updates
@Jason, for the moment, you can download driver from AMD directly. http://support.amd.com/en-us/download -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1308954 Title: AMDRadeon HD 8670A/8670M/8690M [1002:6660] System freezes after resume from suspend with fglrx-updates Status in HWE Next Project: Triaged Status in HWE Next trusty series: In Progress Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer-updates source package in Trusty: In Progress Bug description: SRU Justification [impact] this bug is blocking us to pass certification on OEM hardware. [test case] 1. Install 14.04 and fglrx-updates driver 2. Suspend the machine 3. Wake it up Expected result: * Everything should work fine before and after S3 [regression potential] - CID: 201305-13624 This system would freeze after resume from suspend with fglrx-updates on Trusty. Steps: 1. Install 14.04, and fglrx-updates driver 2. Suspend 3. Wake it up Expected results: * Everything works fine before / after S3 Actual results: * After S3, I can see the login screen, caps lock LED and touchpad still responsive, but I can't login. Few seconds later, system froze, error message could be found in syslog kernel: [ 599.576267] 3[fglrx:firegl_pplib_notify_event] *ERROR* PPLIB: PPLib Notify Event failed! kernel: [ 599.576268] 3[fglrx:firegl_pplib_notify_event] *ERROR* ulEventType = 0002, ulEventData = ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fglrx-updates 2:13.350.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .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 CurrentDesktop: Unity Date: Thu Apr 17 16:42:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-23-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-24-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-10 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=ef6ba3b5-e12b-4029-9d6b-cb1753a88ce5 ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer-updates UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.fglrx-installer: fglrx-installer N/A 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: Thu Apr 17 16:31:44 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error:
[Desktop-packages] [Bug 106573] Re: can only add a single key combination to the keyboard shortcut applet
** Changed in: gnome-control-center Status: New = Confirmed -- 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/106573 Title: can only add a single key combination to the keyboard shortcut applet Status in GNOME Control Center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: On Ubuntu Feisty -- and I presume all older variants -- each action in the Keyboard Shortcuts applet can have only single shortcut attached. (The program is gnome-keybinding-properties.) There should be at least a pair of primary/secondary shortcuts for each action. (See for example Amarok's global shortcuts.) Example usage: I touch-type, and I usually have lots of shortcuts all over the keyboard that can be very easily typed when doing other work. However, many of them are hard to press one-handed, for example when I'm not working and I just want to skip a track. The reverse is also true: key combinations that are easy to press one-handed are unpleasant to use when touch-typing: these are touches close to the corners, and they need some finger-twisting to reach. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/106573/+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 1003950] Re: launcher does not show minimized update manager while clicked
Here's another symptom, though it may well be unrelated. This bug affects my work computer, on which I have ubuntu 14.04 LTS, 64-bit. On that computer, when I use the workaround, i.e., quit software updater and start it, a window appears for it and I can use it to update. But the window can't be resized. The mouse pointer doesn't even change when I pass it over the window's border. -- 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/1003950 Title: launcher does not show minimized update manager while clicked Status in Compiz: New Status in Accelerated Xorg driver for nVidia cards: New Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in binary-driver-fglrx package in Ubuntu: New Status in intel-linux-graphics-installer package in Ubuntu: New Status in unity package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Status in binary-driver-fglrx source package in Precise: New Status in intel-linux-graphics-installer source package in Precise: New Status in unity source package in Precise: Fix Released Status in update-manager source package in Precise: Confirmed Status in xserver-xorg-video-nouveau source package in Precise: New Status in binary-driver-fglrx source package in Quantal: Invalid Status in intel-linux-graphics-installer source package in Quantal: Invalid Status in unity source package in Quantal: Fix Released Status in update-manager source package in Quantal: Won't Fix Status in xserver-xorg-video-nouveau source package in Quantal: Invalid Bug description: Found an easy way to reproduce it during brussels sprint: 1. start deja-dup or update-manager 2. kill -9 compiz; metacity 3. compiz --replace === Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1003950/+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
Re: [Desktop-packages] [Bug 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives
screen flicker on 'Toshiba Satelite A215-S4697' 1. kernel 3.19.0 - versions 7,8,9: ubuntu 15.10 screen does not flicker at all 2. kernel 3.13.0 a. uptil version 35 (36?): screen does not flicker b. upwards from version 36 screen flickers badlyc. (upwards from version 36 a bug - or omission - may have crept in) On Thursday, March 19, 2015 3:42 PM, jwm hogenboom bandarsla...@yahoo.com wrote: kernel versions on 'Satelite A215-S4697' related On Monday, March 9, 2015 12:12 PM, jwm hogenboom bandarsla...@yahoo.com wrote: 1. i installed a brandnew 'crucial ssd' on this 'toshiba satelite A215-S4697' - hoping that disk speed would solve the problem 2. first distro installed was 'zorin 9 lite'3. the original installation did not flicker: kernel 3.13.32 (??)4. the updated kernel version flickered badly: kernel 3.13.46 'zorin' is based on 'ubuntu 14.04 xfce' On Friday, February 27, 2015 2:01 PM, jwm hogenboom bandarsla...@yahoo.com wrote: 1. the same still holds for all ubuntu 14.04.2 - and all of its derivatives2. the flickering does not exist in the very first - and original - kernel of ubuntu 14.043. the flickering does not exist in 'linux mint 17.0' - since 'mint' does not change kernels, the way ubuntu does On Monday, February 23, 2015 5:20 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: hansie, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1405277 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. As well, given the information from the prior release is already available, testing a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1405277 Title: screen flicker in ubuntu 14.04.1 and derivatives Status in xorg package in Ubuntu: Incomplete Bug description: 1. my screen flickers on all ubuntu 14.04.1 distro versions, linux mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc. 2. it flickers on the mint 17.1 'cinamon' installation disk - but it is stable on mint 17.0 'mate' installed 3. i can cure it by accesing the 'recovery section' of the 'multi- boot' system: but it is NOT 'persistent' 4. how can i fix this, using the 'cli': to make the fix 'permanent' the laptop is an older 'toshiba - amd - athlon x2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1405277 Title: screen flicker in ubuntu 14.04.1 and derivatives Status in xorg package in Ubuntu: Incomplete Bug description: 1. my screen flickers on all ubuntu 14.04.1 distro versions, linux mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc. 2. it flickers on the mint 17.1 'cinamon' installation disk - but it is stable on mint 17.0 'mate' installed 3. i can cure it by accesing the 'recovery section' of the 'multi- boot' system: but it is NOT 'persistent' 4. how can i fix this, using the 'cli': to make the fix 'permanent' the laptop is an older 'toshiba - amd - athlon x2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+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 1431654] Re: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage
The bug fixed for me on Linux paz 3.2.0-79-generic-pae #115-Ubuntu SMP Thu Mar 12 14:33:25 UTC 2015 i686 i686 i386 GNU/Linux Thank you very much! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1431654 Title: lightdm (1.2.3-0ubuntu2.6) 100%/high cpu usage Status in lightdm package in Ubuntu: Fix Committed Bug description: Since updating lightdm today, one core of my CPU is always maxed out at 100%. I rolled back to version 1.2.3-0ubuntu2.5 and the issue stopped. I tried this with 2 different kernels: 3.2.0-77-generic and 3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still caused 100% cpu usage. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.6 ProcVersionSignature: Ubuntu 3.2.0-77.114-generic 3.2.66 Uname: Linux 3.2.0-77-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Thu Mar 12 20:20:12 2015 ExecutablePath: /usr/sbin/lightdm InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+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 1434321] [NEW] cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
Public bug reported: apport reported that this crashed on startup. This has happened since re-installation of 15.04 with systemd. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 CupsErrorLog: Date: Tue Mar 17 21:55:57 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-03-15 (4 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150314) Lpstat: device for PDF: cups-pdf:/ MachineType: TOSHIBA Satellite C55D-A Papersize: letter PpdFiles: PDF: Generic CUPS-PDF Printer ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed root=UUID=b6a678ff-8cee-42c1-aa03-ae411b3e10da ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f6b69f6b15a: movl $0x1,0xa8(%rax) PC (0x7f6b69f6b15a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd01/27/2014:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-02U005:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55D-A dmi.product.version: PSCFWU-02U005 dmi.sys.vendor: TOSHIBA ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1434321 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() Status in cups-filters package in Ubuntu: New Bug description: apport reported that this crashed on startup. This has happened since re-installation of 15.04 with systemd. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 CupsErrorLog: Date: Tue Mar 17 21:55:57 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-03-15 (4 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150314) Lpstat: device for PDF: cups-pdf:/ MachineType: TOSHIBA Satellite C55D-A Papersize: letter PpdFiles: PDF: Generic CUPS-PDF Printer ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed root=UUID=b6a678ff-8cee-42c1-aa03-ae411b3e10da ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f6b69f6b15a:movl $0x1,0xa8(%rax) PC (0x7f6b69f6b15a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC
[Desktop-packages] [Bug 1160569]
Distro: Slackware 14.1 32bit Libc: glibc-2.20-i486-2 Kernel: 3.12.38 hackman@terion:~$ firefox -version (process:22214): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed Mozilla Firefox 36.0.1 hackman@terion:~$ thunderbird -version (process:22231): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed Thunderbird 31.5.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1160569 Title: GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed Status in The Mozilla Firefox Browser: Confirmed Status in The G Library - GLib: Unknown Status in apport package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Triaged Bug description: Have a look at the screen-shot for more details. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 19.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.9.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BuildID: 20130308124351 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable Date: Tue Mar 26 21:48:57 2013 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-03-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64+mac (20130326) IpRoute: default via 10.0.1.1 dev eth0 proto static 10.0.1.0/24 dev eth0 proto kernel scope link src 10.0.1.16 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True Plugins: Windows Media Player Plug-in 10 (compatible; Videos) - /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla) VLC Multimedia Plugin (compatible Videos 3.6.3) - /usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla) DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so (totem-mozilla) QuickTime Plug-in 7.6.6 - /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=19.0.2/20130308124351 RelatedPackageVersions: totem-mozilla 3.6.3-0ubuntu4 rhythmbox-mozilla 2.98-0ubuntu3 RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1160569/+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 1433931] Re: nm-applet crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1418260 *** https://bugs.launchpad.net/bugs/1418260 Dear apport retracing service. You have marked this bug as a duplicate of a private bug. I cannot POSSIBLY comment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1433931 Title: nm-applet crashed with SIGSEGV in g_main_context_dispatch() Status in network-manager-applet package in Ubuntu: New Bug description: Update 14.10 to 15.04 beta Reboot onto 3.19.0 kernel (automatic on login) Reassociate with a WLAN Crash. Kapow. Bam. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: network-manager-gnome 0.9.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 00:28:30 2015 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) IpRoute: default via 10.1.10.1 dev wlan0 proto static metric 1024 10.1.10.0/24 dev wlan0 proto kernel scope link src 10.1.10.43 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4327a0: mov0x18(%r14),%rdi PC (0x004327a0) ok source 0x18(%r14) (0x0018) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager-applet StacktraceTop: ?? () ?? () ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nm-applet crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Double Rainbow 04cf0aca-9dff-4a80-95eb-37cdfed683ec /org/freedesktop/NetworkManager/ActiveConnection/0 cdc-wdm0 gsm disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1433931/+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 1190344] Re: Daemon end of session/greeter pipes not closed
Still fixed in 1.2.3-0ubuntu2.7 ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1190344 Title: Daemon end of session/greeter pipes not closed Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Fix Committed Status in lightdm source package in Trusty: Fix Released Status in lightdm source package in Utopic: Fix Released Status in lightdm source package in Vivid: Fix Released Status in Fedora: Unknown Bug description: [Impact] LightDM doesn't close the server side end of the pipes used to communicate with session processes and greeters. This means each session/greeter that is created leaks two file descriptors eventually leading to the system stopping it from creating new pipes. [Test Case] 1. Start LightDM 2. Check how many pipes are open # lsof -p {lightdm_pid} | grep FIFO | wc -l 3. Create sessions by either cycling between users in Unity Greeter or logging in and out 4. Check how many pipes exist using step 2. Expected result: No more pipes should be open Observed result: Many pipes remain open [Regression Potential] Low. Fix is to close pipes when finished with them. Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1069218] Re: users.conf doesn't match users.c
Still working with 1.2.3-0ubuntu2.7 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1069218 Title: users.conf doesn't match users.c Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in Light Display Manager 1.8 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Fix Committed Status in lightdm source package in Trusty: Fix Released Bug description: [Impact] The default users.conf provided by LightDM mentions a section [UserAccounts]. It should be [UserList]. [Test Case] 1. Check default installed users.conf Expected result: Should have a [UserList] section with all items available but disabled. Observed result: Have a [UserAccounts] section with all items available but disabled. [Regression Potential] Very low - just changing the default configuration file which has no active configuration items. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1069218/+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 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1235915 Title: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server() Status in Light Display Manager: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in Light Display Manager 1.4 series: Fix Committed Status in Light Display Manager 1.8 series: Fix Committed Status in indicator-keyboard package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in indicator-keyboard source package in Precise: New Status in lightdm source package in Precise: Fix Committed Bug description: The bug report details have been generated automatically. I'm not sure if this bug happens with lightdm or later on. The System Problem Detected dialogue box appears about 15 to 20 seconds after I've logged in (without me running any apps), so it could be that the crash occurs in the lightdm log-in screen but it just takes my system a while to collect the bug info? Everything appears to work normally after the System Problem Detected dialogue, so whatever is crashing seems to restart gracefully. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 11:15:17 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service InstallationDate: Installed on 2013-09-28 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk --use-bamf ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax PC (0x7fa5a9482616) ok source 0x18(%rdx) (0x0018) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-keyboard StacktraceTop: ?? () from /usr/lib/libxklavier.so.16 lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0 lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0 ?? () ?? () Title: indicator-keyboard-service crashed with SIGSEGV in lightdm_get_layouts() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1235915/+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 1207935] Re: lightdm crashed with SIGSEGV in quit_timeout_cb()
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1207935 Title: lightdm crashed with SIGSEGV in quit_timeout_cb() Status in Light Display Manager: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Fix Committed Bug description: .. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.8-0ubuntu1 Uname: Linux 3.11.0-031100rc3-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Jul 31 00:29:44 2013 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2011-07-23 (738 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu autologin-user= MarkForUpload: True ProcCmdline: lightdm ProcEnviron: TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x40e47d: movl $0x0,0x20(%rax) PC (0x0040e47d) ok source $0x0 ok destination 0x20(%rax) (0xaaca) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: lightdm StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: lightdm crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to saucy on 2013-07-10 (19 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1207935/+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 1434108] Re: Libre Writer export to PDF error
Clon, thank you for reporting this and helping make Ubuntu better. Could you please advise which character(s) specifically are shifted? As well, what program are you opening the PDF with? ** Changed in: libreoffice (Ubuntu) Importance: Undecided = Low ** Changed in: libreoffice (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1434108 Title: Libre Writer export to PDF error Status in libreoffice package in Ubuntu: Incomplete Bug description: When i export document with TheMix font ( http://www.lucasfonts.com/fonts/themix/themix ) some characters are shifted together. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libreoffice-core 1:4.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CurrentDesktop: LXDE Date: Thu Mar 19 15:06:32 2015 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2013-03-16 (733 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1434108/+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 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()
** Tags removed: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1235915 Title: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server() Status in Light Display Manager: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in Light Display Manager 1.4 series: Fix Committed Status in Light Display Manager 1.8 series: Fix Committed Status in indicator-keyboard package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in indicator-keyboard source package in Precise: New Status in lightdm source package in Precise: Fix Committed Bug description: The bug report details have been generated automatically. I'm not sure if this bug happens with lightdm or later on. The System Problem Detected dialogue box appears about 15 to 20 seconds after I've logged in (without me running any apps), so it could be that the crash occurs in the lightdm log-in screen but it just takes my system a while to collect the bug info? Everything appears to work normally after the System Problem Detected dialogue, so whatever is crashing seems to restart gracefully. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 11:15:17 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service InstallationDate: Installed on 2013-09-28 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk --use-bamf ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax PC (0x7fa5a9482616) ok source 0x18(%rdx) (0x0018) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-keyboard StacktraceTop: ?? () from /usr/lib/libxklavier.so.16 lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0 lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0 ?? () ?? () Title: indicator-keyboard-service crashed with SIGSEGV in lightdm_get_layouts() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1235915/+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 1428972] Re: Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2
I installed the nvidia-driver-346.47 after adding xorg-edgers ppa (using sudo add-apt-repository ppa:xorg-edgers/ppa ) to my system. Wanted to setup packages for openGL development. While trying to install freeglut3-dev I get the following message: // Terminal Output === The following packages have unmet dependencies: unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. // Terminal Output === Giving: sudo apt-get -o Debug::pkgProblemResolver=yes dist-upgrade outputs: Terminal Output === Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libgl1-mesa-dri-lts-utopic [ amd64 ] 10.3.2-0ubuntu1~trusty2 ( libs ) Broken libgl1-mesa-dri-lts-utopic:amd64 Conflicts on libgl1-mesa-dri [ amd64 ] none - 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz~trusty ( libs ) Considering libgl1-mesa-dri:amd64 6 as a solution to libgl1-mesa-dri-lts-utopic:amd64 13 Added libgl1-mesa-dri:amd64 to the remove list Conflicts//Breaks against version 10.1.3-0ubuntu0.3 for libgl1-mesa-dri but that is not InstVer, ignoring Conflicts//Breaks against version 10.1.0-4ubuntu5 for libgl1-mesa-dri but that is not InstVer, ignoring Fixing libgl1-mesa-dri-lts-utopic:amd64 via keep of libgl1-mesa-dri:amd64 Investigating (0) libgbm1 [ amd64 ] 10.1.3-0ubuntu0.3 - 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz~trusty ( libs ) Broken libgbm1:amd64 Depends on libgl1-mesa-dri [ amd64 ] none - 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz~trusty ( libs ) (= 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz~trusty) Considering libgl1-mesa-dri:amd64 6 as a solution to libgbm1:amd64 0 Holding Back libgbm1:amd64 rather than change libgl1-mesa-dri:amd64 Try to Re-Instate (1) libgbm1:amd64 Done Done Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages have been kept back: libgbm1 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Terminal Output === Trying to install freeglut3-dev through synaptic package manager suggest I should delete the following packages: account-plugin-aim account-plugin-jabber account-plugin-salut account-plugin-yahoo cheese empathy gir1.2-totem-1.0 gnome-contacts gstreamer1.0-clutter indicator-bluetooth libcheese-gtk23 libcheese7 libclutter-1.0-0 libclutter-gst-2.0-0 libclutter-gtk-1.0-0 libcogl-pango15 ...and many more Trying to install cuda sdk 7 also ouputs the same message at the beginning of this comment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1428972 Title: Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2 Status in unity-control-center package in Ubuntu: Confirmed Bug description: I bumped into this issue while trying to install canonical- certification-client from our PPA [1] ubuntu@201307-13942:~$ sudo apt-get install canonical-certification-client Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. However, the version number for these two packages are bigger than the required version number: ubuntu@201307-13942:~$ dpkg -l | grep libcheese-gtk23 ii libcheese-gtk23:amd64 3.10.2-0ubuntu2 amd64tool to take pictures and videos from your webcam - widgets ubuntu@201307-13942:~$ dpkg -l | grep libcheese7 ii libcheese7:amd64 3.10.2-0ubuntu2 amd64tool to take pictures and videos from your webcam - base library ubuntu@201307-13942:~$ I have no clue for how this happens. I
Re: [Desktop-packages] [Bug 1405277] Re: screen flicker in ubuntu 14.04.1 and derivatives
kernel versions on 'Satelite A215-S4697' related On Monday, March 9, 2015 12:12 PM, jwm hogenboom bandarsla...@yahoo.com wrote: 1. i installed a brandnew 'crucial ssd' on this 'toshiba satelite A215-S4697' - hoping that disk speed would solve the problem 2. first distro installed was 'zorin 9 lite'3. the original installation did not flicker: kernel 3.13.32 (??)4. the updated kernel version flickered badly: kernel 3.13.46 'zorin' is based on 'ubuntu 14.04 xfce' On Friday, February 27, 2015 2:01 PM, jwm hogenboom bandarsla...@yahoo.com wrote: 1. the same still holds for all ubuntu 14.04.2 - and all of its derivatives2. the flickering does not exist in the very first - and original - kernel of ubuntu 14.043. the flickering does not exist in 'linux mint 17.0' - since 'mint' does not change kernels, the way ubuntu does On Monday, February 23, 2015 5:20 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: hansie, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1405277 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. As well, given the information from the prior release is already available, testing a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1405277 Title: screen flicker in ubuntu 14.04.1 and derivatives Status in xorg package in Ubuntu: Incomplete Bug description: 1. my screen flickers on all ubuntu 14.04.1 distro versions, linux mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc. 2. it flickers on the mint 17.1 'cinamon' installation disk - but it is stable on mint 17.0 'mate' installed 3. i can cure it by accesing the 'recovery section' of the 'multi- boot' system: but it is NOT 'persistent' 4. how can i fix this, using the 'cli': to make the fix 'permanent' the laptop is an older 'toshiba - amd - athlon x2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1405277 Title: screen flicker in ubuntu 14.04.1 and derivatives Status in xorg package in Ubuntu: Incomplete Bug description: 1. my screen flickers on all ubuntu 14.04.1 distro versions, linux mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc. 2. it flickers on the mint 17.1 'cinamon' installation disk - but it is stable on mint 17.0 'mate' installed 3. i can cure it by accesing the 'recovery section' of the 'multi- boot' system: but it is NOT 'persistent' 4. how can i fix this, using the 'cli': to make the fix 'permanent' the laptop is an older 'toshiba - amd - athlon x2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+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 1433032] Re: Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins
Reinstalled `gnome-keyring` and upgraded Chrome to v42 beta. Load time seems decreased. Regards respect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1433032 Title: Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins Status in gnome-keyring package in Ubuntu: Confirmed Bug description: This is Ubuntu 14.04 LTS x64. I removed good amount of remembered passwords but there are no noticable changes. Chrome is v 40.0.2214.10 beta (64-bit) --- Regards respect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1433032/+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 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
1) Run Ubuntu 14.04.2 LiveUSB 2) Try to install QtCreator Result: apt tells unmet dependencies -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Trusty: Fix Committed Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+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 1422132] [NEW] Canoscan LIDE 20 (plustek backend) not working anymore
You have been subscribed to a public bug: I don't know when it happened, but through some upgrade my scanner has lost function here. There is no movement inside, it only scans a black image. Sometimes, rarely I can scan one, but only one image, but directly afterwards it gives up again. It does not depend on the pc, because I see the same result on three different laptops but all with actual Ubuntu 14.04. Using a live version of 14.04.1 from July 2014 everything works fine. lsb_release -rd Description:Ubuntu 14.04.1 LTS apt-cache policy sane *** 1.0.14-9 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-45.74-lowlatency 3.13.11-ckt13 Uname: Linux 3.13.0-45-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 15 17:09:39 2015 InstallationDate: Installed on 2014-07-27 (202 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug third-party-packages trusty -- Canoscan LIDE 20 (plustek backend) not working anymore https://bugs.launchpad.net/bugs/1422132 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 448587] Re: Scanner from Epson DX8400 MFP ignored by sane
Hallo, Ubuntu 9.10 is outdated. If this back still exists please file a new bug against sane-backends. CU Jörg ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New = Invalid -- 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/448587 Title: Scanner from Epson DX8400 MFP ignored by sane Status in sane-backends package in Ubuntu: Invalid Bug description: The scanner from the Epson DX8400 used to be handled by the libsane- extras package, but it is now completely ignored. Packages like xsane only see my Logitech webcam (UVC). ProblemType: Bug Architecture: i386 Date: Sun Oct 11 11:07:31 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: sane 1.0.14-7 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: sane-frontends Uname: Linux 2.6.31-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/448587/+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 365064] Re: no lineart mode for scanner canon mp610
Ubuntu 9.04 is outdatet. If this back still exists please file a new back against sane-backends. CU Jörg ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New = Invalid -- 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/365064 Title: no lineart mode for scanner canon mp610 Status in xsane: New Status in sane-backends package in Ubuntu: Invalid Bug description: there is no lineart (b/w) mode available in xsane and other scan- tools. gray and color modes work perfect. using canon scan gear mp drivers v1.10-1. the problem was in intrepid too. packages: sane 1.0.14-7 xsane 0.996-1ubuntu2 ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: sane 1.0.14-7 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: sane-frontends Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/xsane/+bug/365064/+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 448587] Re: Scanner from Epson DX8400 MFP ignored by sane
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New = Confirmed -- 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/448587 Title: Scanner from Epson DX8400 MFP ignored by sane Status in sane-backends package in Ubuntu: Invalid Bug description: The scanner from the Epson DX8400 used to be handled by the libsane- extras package, but it is now completely ignored. Packages like xsane only see my Logitech webcam (UVC). ProblemType: Bug Architecture: i386 Date: Sun Oct 11 11:07:31 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: sane 1.0.14-7 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: sane-frontends Uname: Linux 2.6.31-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/448587/+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 1432976] Re: Battery hot key does not bring up the power management dialog in Trusty
** Also affects: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1432976 Title: Battery hot key does not bring up the power management dialog in Trusty Status in HWE Next Project: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Trusty: New Bug description: * Impact the battery hotkey doesn't do anything * Test case: On a laptop with a special key for battery info press fn+f3 - the power info dialog should be displayed * Regression potential the action used before was buggy, having a valid one shouldn't create any issue -- CID: 201209-11840 Dell L322X The battery hotkey on this system (fn+f3) cannot bring up the power management dialog. Also verified with 14.04.2 on LiveUSB, it's not working as well. But it works with 12.04.5 on LiveUSB. (Maybe it's user-space related?) It seems that the key event could be detected properly, it could pass our checkbox test (which will check the '0xe071,0xef1:Battery Info' signal) ubuntu@201209-11840:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 240 press keycode 240 release keycode 238 press keycode 238 release keycode 29 press ^Ccaught signal 2, cleaning up... ubuntu@201209-11840:~$ ubuntu@201209-11840:~$ sudo showkey -s kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... 0x9c 0xe0 0x71 0xe0 0xf1 ^Ccaught signal 2, cleaning up... ubuntu@201209-11840:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1568 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Mar 17 03:29:53 2015 HibernationDevice: RESUME=UUID=de4c68b6-83dc-477e-98f1-1696b3233a48 InstallationDate: Installed on 2015-03-13 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. XPS L322X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=4039eaa6-fdf4-423a-ace9-930a8911122e ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1432976/+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 365064] Re: no lineart mode for scanner canon mp610
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New = Confirmed -- 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/365064 Title: no lineart mode for scanner canon mp610 Status in xsane: New Status in sane-backends package in Ubuntu: Invalid Bug description: there is no lineart (b/w) mode available in xsane and other scan- tools. gray and color modes work perfect. using canon scan gear mp drivers v1.10-1. the problem was in intrepid too. packages: sane 1.0.14-7 xsane 0.996-1ubuntu2 ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: sane 1.0.14-7 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: sane-frontends Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/xsane/+bug/365064/+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 1433943] Re: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid)
We will not enable this in the Google key shipped with the google.provider file, because that key should only be used for validating the account creation. GNOME Evolution ships the google-contacts.service file which you seem to be using, so that could be a candidate for adding the permission. I've already enabled the CardDav access on the Google API console, so it's just a matter of modifying the google-contacts.service file and adding the additional scope there. ** Project changed: account-plugins = evolution-data-server (Ubuntu) ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided = Medium ** Changed in: evolution-data-server (Ubuntu) Status: New = Confirmed ** Changed in: evolution-data-server (Ubuntu) Assignee: (unassigned) = Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1433943 Title: Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid) Status in evolution-data-server package in Ubuntu: Confirmed Bug description: It seems Ubuntu does not enable CardDav scope (https://www.googleapis.com/auth/carddav) in online account. Ubuntu only enables Google Contacts API (Gdata) https://www.google.com/m8/feeds/ which is NOT same as CardDav. As a result when some application( ex. Syncevolution) tries to access it (through oauth2), it gives “authentication failed error”. For example, running following command: ''' SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\ loglevel=2 backend=carddav username=uoa:3,google-contacts\ syncURL=https://www.googleapis.com/.well-known/carddav ''' gives following error: “PROPFIND: Neon error code 1: 403 Forbidden, must not retry” NOTE: It is required that that the scope for accessing CardDAV needs to be specified in the sources too. Having it only in the APIs Console is not enough. Otherwise Google rejects access to the CardDAV resources with a 401 AuthSub challenge. Discussion on Syncevolution Mailing List: https://lists.syncevolution.org/pipermail/syncevolution/2015-March/005119.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1433943/+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 1029410] Re: 2 scanners, 1 not visible to user, only root can see it
Hello Gene, I set the package to sane-backends. can you tell me whats your changes at udev/rules.d? Thanks Jörg ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New = Incomplete -- 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/1029410 Title: 2 scanners, 1 not visible to user, only root can see it Status in sane-backends package in Ubuntu: Incomplete Bug description: I am not sure what to shake a finger at, but I fixed it with a udev file not supplied by ubuntu ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 2.6.32-122.35.rtai-rtai 2.6.32.11+drm33.2 Uname: Linux 2.6.32-122-rtai i686 Architecture: i386 Date: Thu Jul 26 07:53:10 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: sane-frontends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1029410/+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 1433931] Re: nm-applet crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1418260 *** https://bugs.launchpad.net/bugs/1418260 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1418260, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1433931/+attachment/4349636/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1433931/+attachment/4349638/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1433931/+attachment/4349647/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1433931/+attachment/4349648/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1433931/+attachment/4349649/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1433931/+attachment/4349651/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1433931/+attachment/4349652/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1418260 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1433931 Title: nm-applet crashed with SIGSEGV in g_main_context_dispatch() Status in network-manager-applet package in Ubuntu: New Bug description: Update 14.10 to 15.04 beta Reboot onto 3.19.0 kernel (automatic on login) Reassociate with a WLAN Crash. Kapow. Bam. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: network-manager-gnome 0.9.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 00:28:30 2015 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) IpRoute: default via 10.1.10.1 dev wlan0 proto static metric 1024 10.1.10.0/24 dev wlan0 proto kernel scope link src 10.1.10.43 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: nm-applet ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4327a0: mov0x18(%r14),%rdi PC (0x004327a0) ok source 0x18(%r14) (0x0018) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager-applet StacktraceTop: ?? () ?? () ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nm-applet crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Double Rainbow 04cf0aca-9dff-4a80-95eb-37cdfed683ec /org/freedesktop/NetworkManager/ActiveConnection/0 cdc-wdm0 gsm disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1433931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1366429] [NEW] no scanners reported by sane BR-7065DN
You have been subscribed to a public bug: Printer found and operating properly; No Scanners found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 6 15:50:37 2014 InstallationDate: Installed on 2014-06-01 (97 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug trusty -- no scanners reported by sane BR-7065DN https://bugs.launchpad.net/bugs/1366429 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 1366429] Re: no scanners reported by sane BR-7065DN
Hallo David, I think that No Scanners found comes from sane-backends. I switch it to this package. Please can you run SANE_DEBUG_DLL=3 scanimage -L on a terminal, attach the output here and set the status back to confirmed Thanks Jörg ** Changed in: sane-frontends (Ubuntu) Status: New = Incomplete ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) -- 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/1366429 Title: no scanners reported by sane BR-7065DN Status in sane-backends package in Ubuntu: Incomplete Bug description: Printer found and operating properly; No Scanners found ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 6 15:50:37 2014 InstallationDate: Installed on 2014-06-01 (97 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1366429/+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 1426420] Re: unity-settings daemon notifies as error an info message Edit
Yes, the gnome-settings-daemon package has the same bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1426420 Title: unity-settings daemon notifies as error an info message Edit Status in unity-settings-daemon package in Ubuntu: New Bug description: [This bug is related to bug #1202198] When sending a document to a printer, unity-settings daemon will show a message like: ERROR: connecting to printer Nevertheless, the document will print without any issue. Actually this message is a warning or info message, as it is telling the user that it is connecting to the printer. In Ubuntu 14.10 (Utopic), there are two packages that can be involved in gnome printer norifications: gnome-settings-daemon and unity- settings-daemon. The latter package seems to be a fork of the former, for Unity use I suppose. These two packages come with a printer notification plugin. The one of gnome-settings-daemon is /usr/lib/gnome-settings-daemon/gsd-printer and the other is /usr/lib/unity-settings-daemon/usd-printer. I found that if the gnome-flashback session (a.ka. Gnome Classic) is used, the printer notification plugin involved is usd-printer, from the unity-settings-daemon package. I guess that gsd-printer is used in a Gnome Shell session (I don't use it so I can test my guessing). So, to remove the connecting-to-printer false error message, I think the safest approach is to patch both packages, just by adding the lines: if (g_str_has_prefix (reason, connecting-to-device)) return TRUE; to the reason_is_blacklisted() static function in gsd-print- notifications-manager.c. A patch is attached for the gnome-settings-daemon package and I'll also fill a bug report with a patch for the unity-settings-daemon package. Ubuntu 14.10 unity-settings-daemon_14.04.0+14.10.20141014-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1426420/+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 365064] [NEW] no lineart mode for scanner canon mp610
You have been subscribed to a public bug: there is no lineart (b/w) mode available in xsane and other scan-tools. gray and color modes work perfect. using canon scan gear mp drivers v1.10-1. the problem was in intrepid too. packages: sane 1.0.14-7 xsane 0.996-1ubuntu2 ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: sane 1.0.14-7 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: sane-frontends Uname: Linux 2.6.28-11-generic i686 ** Affects: xsane Importance: Undecided Status: New ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug i386 -- no lineart mode for scanner canon mp610 https://bugs.launchpad.net/bugs/365064 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 448587] [NEW] Scanner from Epson DX8400 MFP ignored by sane
You have been subscribed to a public bug: The scanner from the Epson DX8400 used to be handled by the libsane- extras package, but it is now completely ignored. Packages like xsane only see my Logitech webcam (UVC). ProblemType: Bug Architecture: i386 Date: Sun Oct 11 11:07:31 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: sane 1.0.14-7 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: sane-frontends Uname: Linux 2.6.31-13-generic i686 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug i386 -- Scanner from Epson DX8400 MFP ignored by sane https://bugs.launchpad.net/bugs/448587 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 1433942] Re: nautilus crashed with SIGSEGV in g_closure_invalidate()
*** This bug is a duplicate of bug 1431073 *** https://bugs.launchpad.net/bugs/1431073 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1431073, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1433942/+attachment/4349679/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1433942/+attachment/4349681/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1433942/+attachment/4349682/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1433942/+attachment/4349683/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1433942/+attachment/4349684/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1433942/+attachment/4349685/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1433942/+attachment/4349686/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1431073 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1433942 Title: nautilus crashed with SIGSEGV in g_closure_invalidate() Status in nautilus package in Ubuntu: New Bug description: Crash when closing nautilus window. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 19 15:57:07 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-04-22 (331 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7f75a47c7d92:cmp%rbp,0x28(%rax) PC (0x7f75a47c7d92) ok source %rbp ok destination 0x28(%rax) (0x0028) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invalidate () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_closure_invalidate() UpgradeStatus: Upgraded to vivid on 2015-03-12 (6 days ago) UserGroups: adm autopilot cdrom dip docker libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1433942/+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 1422132] Re: Canoscan LIDE 20 (plustek backend) not working anymore
Hallo David, I think that this bug comes from sane-backends. I switch it to this package. Please can you run SANE_DEBUG_DLL=3 scanimage -L on a terminal, attach the output here and set the status back to confirmed Thanks Jörg ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New = Incomplete -- 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/1422132 Title: Canoscan LIDE 20 (plustek backend) not working anymore Status in sane-backends package in Ubuntu: Incomplete Bug description: I don't know when it happened, but through some upgrade my scanner has lost function here. There is no movement inside, it only scans a black image. Sometimes, rarely I can scan one, but only one image, but directly afterwards it gives up again. It does not depend on the pc, because I see the same result on three different laptops but all with actual Ubuntu 14.04. Using a live version of 14.04.1 from July 2014 everything works fine. lsb_release -rd Description: Ubuntu 14.04.1 LTS apt-cache policy sane *** 1.0.14-9 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-45.74-lowlatency 3.13.11-ckt13 Uname: Linux 3.13.0-45-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 15 17:09:39 2015 InstallationDate: Installed on 2014-07-27 (202 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1422132/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
Gunnar, the FFe for this wasn't approved so language-selector shouldn't have been uploaded. We wanted to verify that the approach is sensible first. Seems that it luckily is, so retrospectively granted, but please be aware in future. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed = Fix Released ** Changed in: language-selector (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1433858] Re: Mouse cursor flickering when using two graphics cards
Jonathan Wang, thank you for reporting this and helping make Ubuntu better. Could you please test http://cdimage.ubuntu.com/daily- live/current/ and advise to the results? ** Changed in: xorg (Ubuntu) Importance: Undecided = Medium ** Changed in: xorg (Ubuntu) Status: New = Incomplete ** Description changed: - See bug #1278223 + Mouse cursor flickering when using two monitors. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.7 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 CurrentDesktop: Unity Date: Wed Mar 18 22:40:10 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: - Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821] - Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:042c] + Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821] + Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:042c] InstallationDate: Installed on 2015-02-24 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: MSI MS-7821 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=cb3bd3ad-4c60-460e-8982-45ab28abdaf2 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-G45 GAMING (MS-7821) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd11/10/2014:svnMSI:pnMS-7821:pvr1.0:rvnMSI:rnZ97-G45GAMING(MS-7821):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7821 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Mar 18 14:17:36 2015 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 xserver.video_driver: radeon ** Description changed: - Mouse cursor flickering when using two monitors. + Mouse cursor flickering when using two graphics cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 CurrentDesktop: Unity Date: Wed Mar 18 22:40:10 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7821] Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:042c] InstallationDate: Installed on 2015-02-24 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: MSI MS-7821 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=cb3bd3ad-4c60-460e-8982-45ab28abdaf2 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw
[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works
Jeroen T. Vermeulen, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test 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 bug 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-3.XY-rcZ Where XY and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.XY-rcZ Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Package changed: xorg (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in linux package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 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 CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-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-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core:
[Desktop-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users
On 2015-03-19 10:42, Iain Lane wrote: Gunnar, the FFe for this wasn't approved so language-selector shouldn't have been uploaded. Sorry Iain, forgot that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Fix Committed Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1433935] [NEW] Ubuntu 14.04 Software Center still proposes V0.48
Public bug reported: Hi, Can you do anything to get the Ubuntu Software Center to propose the latest version of Inkscape ? I use Hershey Text and the extension doesn't seem to work with V0.48, I want to install the V0.91 but I don't want to have to compile from sources... If there's another way of getting the V0.91 package (link to the .deb ?) I'd be grateful. ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New -- 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/1433935 Title: Ubuntu 14.04 Software Center still proposes V0.48 Status in inkscape package in Ubuntu: New Bug description: Hi, Can you do anything to get the Ubuntu Software Center to propose the latest version of Inkscape ? I use Hershey Text and the extension doesn't seem to work with V0.48, I want to install the V0.91 but I don't want to have to compile from sources... If there's another way of getting the V0.91 package (link to the .deb ?) I'd be grateful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1433935/+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 1370764] [NEW] no scanner Brother DCP-7065DN found by sane
You have been subscribed to a public bug: Brother DCP-7065DN Long existing problem with this printer/scanner printer found and works properly Scanner not found by sane All installed according to Brother scanner install method. Did work remotely for a short time but feel that an update broke it. Ubuntu 14.04 all updates done Lenovo H-535 64 bit 4 core with defeated UEFI Networked via usb through router ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 17 16:05:58 2014 InstallationDate: Installed on 2014-06-01 (108 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- no scanner Brother DCP-7065DN found by sane https://bugs.launchpad.net/bugs/1370764 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 1370764] Re: no scanner Brother DCP-7065DN found by sane
*** This bug is a duplicate of bug 1361908 *** https://bugs.launchpad.net/bugs/1361908 ** Summary changed: - no scanner found by sane + no scanner Brother DCP-7065DN found by sane ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) ** This bug has been marked a duplicate of bug 1361908 Brother- DCP7065-DN printer not found -- 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/1370764 Title: no scanner Brother DCP-7065DN found by sane Status in sane-backends package in Ubuntu: New Bug description: Brother DCP-7065DN Long existing problem with this printer/scanner printer found and works properly Scanner not found by sane All installed according to Brother scanner install method. Did work remotely for a short time but feel that an update broke it. Ubuntu 14.04 all updates done Lenovo H-535 64 bit 4 core with defeated UEFI Networked via usb through router ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 17 16:05:58 2014 InstallationDate: Installed on 2014-06-01 (108 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1370764/+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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
I tested the patch which at #51. The background issue was fixed. And the new code had been uploaded to lp. $ bzr push lp:~oem-solutions-group/kittyhawk/gnome-desktop3.lp1382291 The upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=746044 . The patch was at: https://bugzilla.gnome.org/attachment.cgi?id=299687action=diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in gnome-desktop3 package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in gnome-desktop3 source package in Trusty: Confirmed Status in ubiquity source package in Trusty: Confirmed Bug description: [Impact] The ubiquity window size display in HiDPI screens is small. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. [Test Case] 1. Install image on a system with HiDPI panel 2. Check the ubiquity window size displayed on screen Expected Result: The window size should be reasonable for user to read the content. Actual Result: The window size is small and user is hard to read the content. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+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 1433831] Re: Upstart script doesn't export *_MODULE under Unity 8
The attachment im-config_0.27-1ubuntu8.debdiff seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1433831 Title: Upstart script doesn't export *_MODULE under Unity 8 Status in im-config package in Ubuntu: New Bug description: The IM framework environment variables XMODIFIERS, GTK_IM_MODULE, QT_IM_MODULE, QT4_IM_MODULE, and CLUTTER_IM_MODULE aren't being properly set by the Upstart script under Unity 8. Probably the only reason it's working under most other desktop environments is because it's handled instead by /etc/X11/Xsession.d/70im-config_launch, but it's not getting executed in a Unity 8 Mir session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1433831/+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 1417581] Re: USC - mouse cursor on AMD graphics is drawing incorrectly
** Changed in: mir/0.12 Status: Triaged = Fix Committed ** Changed in: mir/0.12 Assignee: (unassigned) = Andreas Pokorny (andreas-pokorny) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1417581 Title: USC - mouse cursor on AMD graphics is drawing incorrectly Status in Mir: Fix Committed Status in Mir 0.12 series: Fix Committed Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: I've a Lenovo Flex 2 14D, which has an AMD APU. In Unity-System-Compositor, the mouse cursor does not draw correctly. See previous version of this bug for visuals: https://bugs.launchpad.net/mir/+bug/1391975 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1417581/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
The debdiff for setting fcitx as per locale default of zh_*, while restoring ibus as default for everyone else. ** Patch added: im-config_0.27-1ubuntu8.debdiff https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1430893/+attachment/4349739/+files/im-config_0.27-1ubuntu8.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
The meta package itself is not related to pull in fcitx packages, but as ibus-pinyin is removed from desktop-recommends (in 1.333), mark as Fix Released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Fix Committed Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor
** Tags added: needs-apport-collect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I Restore previous settings, after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1387219] Re: Mouse pointer disappears and cursor stops blinking
So is anybody going to do something about this any time soon? Or do we have to wait another 4 years for this to be fixed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in GtkSourceView Widget: Expired Status in anjuta package in Ubuntu: Confirmed Status in gedit package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press CTRLc to cut the text. Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. ***Workaround*** sudo apt-get install ibus-gtk $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1387219/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
Changes for im-config acked at #ubuntu-desktop. ** Changed in: im-config (Ubuntu) Status: Confirmed = Fix Committed ** Changed in: im-config (Ubuntu) Assignee: (unassigned) = Aron Xu (happyaron) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Fix Committed Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1338492] Re: Xorg crashed with SIGABRT in OsAbort()
The seance before this I installed with my micro sd (64Mb) card and set a need string in /etc/fstab file for automounting this new partiotion (FS4) and at start it was OK /dev/sdc5 /media/extra-msd1 ext4 rw,noatime,discard,nosuid,nodev,uhelper=udisks Then I tryed to copy my old archive files to that new partition (sdc5) to make more free space my hard disk (sda1 - FS4). It was very- very slowly (to copy 1 Gb need up to 3 houres) and I did sudo reboot. After that I could-not at first load my first partition linux (ubuntu15.04 - sda1 - 45 Gb) and worked on my second partiton (ubuntu14.04.02 - 48 GB) and after editing /etc/fstab on first part. I may reboted and coming to this variant ubuntu15.04. -- 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/1338492 Title: Xorg crashed with SIGABRT in OsAbort() Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: At startup, my screen flashes in light green, and can't log to lightdm. Adding the ATI driver, it will install with a missing link... Erasing cyrillic path and 75 and 100 dpi path folders. At this time, can't find again the missing link, and just install missings fonts don't fix the bug.. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.15.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.15.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 BootLog: * Setting up X socket directories... [128G [122G[ OK ] * Starting automatic crash report generation: apport [128G [122G[ OK ] 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: Mon Jul 7 10:44:49 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8526] Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 6450 1 GB DDR3 [174b:e164] InstallationDate: Installed on 2014-07-03 (3 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=68f3fab7-5c4e-4d3a-9d6d-a493c47946db ro quiet splash Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x7ffb7ec04db0, argc=11, argv=0x7fff4f6b2e88, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fff4f6b2e78) at libc-start.c:287 Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/07/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5401:bd11/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A55:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 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-1ubuntu4 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: Mon Jul 7 10:48:37 2014 xserver.configfile: default xserver.devices: input
[Desktop-packages] [Bug 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
The issue could be reproduced on 14.04.2. When I tried to install fglrx, it is always failed to navigate to Dash - Additional Drivers - Using Video driver for the AMD graphics accelerators form fglrx. Referee @kaxing's comments #43, it works for me to install fglrx. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 Status in AMD fglrx video driver: Invalid Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Bug description: Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2 Expected behavior: fglrx would intall Observed behavior: fglrx is not installed as follows Attempt to install fglrx fails as follows: zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fglrx-updates : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. Attempt to insatll xorg-video-abi-15 yields: zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Attempting to install xserver-xorg-core instead yields: zack3@ZACK3:~$ sudo apt-get install xserver-xorg-core Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1424491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1433952] Re: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'
*** This bug is a duplicate of bug 1422004 *** https://bugs.launchpad.net/bugs/1422004 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1422004, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** Changed in: hplip (Ubuntu) Importance: Undecided = Medium ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1433952/+attachment/4349718/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1433952/+attachment/4349720/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 1422004 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1433952 Title: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop' Status in hplip package in Ubuntu: New Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: hplip-data 3.15.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 CupsErrorLog: Date: Wed Mar 18 09:13:49 2015 ExecutablePath: /usr/share/hplip/pkservice.py InstallationDate: Installed on 2013-12-22 (451 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) InterpreterPath: /usr/bin/python3.4 Lpstat: device for Canon: dnssd://Canon%20MX920%20series._ipp._tcp.local/?uuid=--1000-8000-F481397AB550 device for HP-Büro-2.0: socket://192.168.45.80:9100 device for HP_LaserJet_M1522n_MFP: hp:/net/HP_LaserJet_M1522n_MFP?ip=192.168.45.80 device for Kyocera-Büro2.0: socket://192.168.45.78:9100 MachineType: LENOVO 429149G PackageArchitecture: all Papersize: a4 PpdFiles: Canon: Canon MX920 series - CUPS+Gutenprint v5.2.10 Kyocera-Büro2.0: Kyocera FS-C5100DN (KPDL) HP_LaserJet_M1522n_MFP: HP LaserJet M1522 MFP Series Postscript (recommended) HP-Büro-2.0: HP LaserJet M1522n MFP Foomatic/pxlmono (recommended) ProcCmdline: /usr/bin/python3 /usr/bin/hp-pkservice ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 PythonArgs: ['/usr/bin/hp-pkservice'] SourcePackage: hplip SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: bluetooth dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1433952/+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 1433943] [NEW] Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid)
You have been subscribed to a public bug: It seems Ubuntu does not enable CardDav scope (https://www.googleapis.com/auth/carddav) in online account. Ubuntu only enables Google Contacts API (Gdata) https://www.google.com/m8/feeds/ which is NOT same as CardDav. As a result when some application( ex. Syncevolution) tries to access it (through oauth2), it gives “authentication failed error”. For example, running following command: ''' SYNCEVOLUTION_DEBUG=1 syncevolution --print-databases –daemon=no\ loglevel=2 backend=carddav username=uoa:3,google-contacts\ syncURL=https://www.googleapis.com/.well-known/carddav ''' gives following error: “PROPFIND: Neon error code 1: 403 Forbidden, must not retry” NOTE: It is required that that the scope for accessing CardDAV needs to be specified in the sources too. Having it only in the APIs Console is not enough. Otherwise Google rejects access to the CardDAV resources with a 401 AuthSub challenge. Discussion on Syncevolution Mailing List: https://lists.syncevolution.org/pipermail/syncevolution/2015-March/005119.html ** Affects: evolution-data-server (Ubuntu) Importance: Medium Assignee: Alberto Mardegan (mardy) Status: Confirmed ** Tags: vivid -- Enable carddav OAuth2 scope ( https://www.googleapis.com/auth/carddav ) in Ubuntu Online Account (Vivid) https://bugs.launchpad.net/bugs/1433943 You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. -- 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 1433167] Re: Acer Aspire ES1-311-C9XM - Synaptics ClickPad soft buttons not configured out of the box
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1433167 Title: Acer Aspire ES1-311-C9XM - Synaptics ClickPad soft buttons not configured out of the box Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: The Acer ES1-311-C9XM is equipped with a Synaptics 'ClickPad', i.e. a touchpad with integrated 'click' button. The default settings assume that the ClickPad is just a normal touchpad with a single hardware mouse button. Basic touchpad functionality is OK. Multitouch features such as two-finger-tap to right-click, and two-finger-swipe to scroll, do work. However, clicking and dragging with the hardware click button, and right-clicking with the hardware click button, do not work. `xinput --list` reports the touchpad as `SYN1B7F:01 06CB:2991 UNKNOWN`. Tweaking settings using `synclient` can fix the problem. For example, to set up the bottom right-hand corner of the touchpad as the software right-click button, we can do the following at a command line: synclient ClickPad=1 synclient RightButtonAreaLeft=610 RightButtonAreaRight=1175 RightButtonAreaTop=489 RightButtonAreaBottom=648 (This configuration is not perfect, and does not persist between reboots - `xorg.conf` editing probably needed for that.) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 17 23:40:41 2015 InstallationDate: Installed on 2015-03-16 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1433167/+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 1432599] Re: Network-manager tries to manage virbr0, which it should not
Here is a bug report, related to the subject: https://bugzilla.gnome.org/show_bug.cgi?id=731014 Notice vboxnet0 also appears in nm-applet, but is shown as Unmanaged, unlike virbr0. ** Bug watch added: GNOME Bug Tracker #731014 https://bugzilla.gnome.org/show_bug.cgi?id=731014 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: New Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+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 1430893] Re: [FFe] Install Fcitx for Chinese users
** Changed in: im-config (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+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 1433945] [NEW] package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: ошибка при обработке пакета lightdm (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 1 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 19 10:46:38 2015 DuplicateSignature: package:lightdm:1.12.3-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-06 (12 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1433945 Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: New Bug description: insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: ошибка при обработке пакета lightdm (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 1 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 19 10:46:38 2015 DuplicateSignature: package:lightdm:1.12.3-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-06 (12 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1433945/+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 1417429] Re: back port signon-plugin-oauth2 Sina weibo fix to rtm
This bug was fixed in the package signon-plugin-oauth2 - 0.20+15.04.20150317~rtm-0ubuntu1 --- signon-plugin-oauth2 (0.20+15.04.20150317~rtm-0ubuntu1) 14.09; urgency=medium [ Alberto Mardegan ] * OAuth2: implement a fallback mechanism when parsing replies (LP: #1417429) -- CI Train Bot ci-train-...@canonical.com Tue, 17 Mar 2015 09:54:51 + ** Changed in: signon-plugin-oauth2 (Ubuntu RTM) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-plugin-oauth2 in Ubuntu. https://bugs.launchpad.net/bugs/1417429 Title: back port signon-plugin-oauth2 Sina weibo fix to rtm Status in the base for Ubuntu mobile products: In Progress Status in signon-plugin-oauth2 package in Ubuntu: In Progress Status in signon-plugin-oauth2 package in Ubuntu RTM: Fix Released Bug description: We have already createtd a RTM (14.10) image for the developers contest in China. Due to some limitation of the Sina weibo API, it wrongly returns the message type (text/plain) which is incorrect for json content. Mardy has fixed the issue, and it is finally landed to vivid. The developers in China is recommended using rtm since it is more stable. The contest started Dec 18th last year, and it will be ended June this year. Sina weibo is an important social network service in China. Some developers may use it for their development for the competition. It is strongly recommended backporting the fix to rtm. This problem happens on RTM image of the phone. it seems that it is a similar bug report as https://bugs.launchpad.net/ubuntu/+source/signon-plugin- oauth2/+bug/1415376 which was fixed for vivid. We need the fix for RTM 14.10 release. Thanks best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417429/+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 1417581] Re: USC - mouse cursor on AMD graphics is drawing incorrectly
** Branch linked: lp:mir/0.12 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1417581 Title: USC - mouse cursor on AMD graphics is drawing incorrectly Status in Mir: Fix Committed Status in Mir 0.12 series: Fix Committed Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: I've a Lenovo Flex 2 14D, which has an AMD APU. In Unity-System-Compositor, the mouse cursor does not draw correctly. See previous version of this bug for visuals: https://bugs.launchpad.net/mir/+bug/1391975 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1417581/+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 1029410] [NEW] 2 scanners, 1 not visible to user, only root can see it
You have been subscribed to a public bug: I am not sure what to shake a finger at, but I fixed it with a udev file not supplied by ubuntu ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 2.6.32-122.35.rtai-rtai 2.6.32.11+drm33.2 Uname: Linux 2.6.32-122-rtai i686 Architecture: i386 Date: Thu Jul 26 07:53:10 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: sane-frontends ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug i386 lucid -- 2 scanners, 1 not visible to user, only root can see it https://bugs.launchpad.net/bugs/1029410 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 1026159] [NEW] Samsung scx4100 no more recognised as scanner
You have been subscribed to a public bug: Samsung scx4100 is a relativelly old but very successful scanner/ laser printer made by Samsung and it's the first of a serie of devices almost identical, where Samsung seems to just change their design and name every year (scx4200, scx4300... scx4600). This kind of devices were initially available to Linux users trough installation of Samsung own drivers, however recent ubuntu releases got able to plug-and-play them, both for printing and scanning (e.g. with simple-scan). While scx4200 or scx4300 still works in this way, on my Ubuntu 12.04 the Samsung scx4100 is no longer available as scanner (but it still plug-and-play as printer). As scx4100 for best of my knowledge is tecnically pretty the same as the other cited printers/scanners of the serie, I guess it just miss entry in some sort of supported devices list. I am available for further informations if needed. Kind regards and thank you. Antonello lsusb: Bus 002 Device 003: ID 04e8:3413 Samsung Electronics Co., Ltd SCX-4100 Scanner ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Wed Jul 18 16:21:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 precise -- Samsung scx4100 no more recognised as scanner https://bugs.launchpad.net/bugs/1026159 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 1026159] Re: Samsung scx4100 no more recognised as scanner
Move to sane-backends ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) -- 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/1026159 Title: Samsung scx4100 no more recognised as scanner Status in sane-backends package in Ubuntu: Confirmed Bug description: Samsung scx4100 is a relativelly old but very successful scanner/ laser printer made by Samsung and it's the first of a serie of devices almost identical, where Samsung seems to just change their design and name every year (scx4200, scx4300... scx4600). This kind of devices were initially available to Linux users trough installation of Samsung own drivers, however recent ubuntu releases got able to plug-and-play them, both for printing and scanning (e.g. with simple-scan). While scx4200 or scx4300 still works in this way, on my Ubuntu 12.04 the Samsung scx4100 is no longer available as scanner (but it still plug-and-play as printer). As scx4100 for best of my knowledge is tecnically pretty the same as the other cited printers/scanners of the serie, I guess it just miss entry in some sort of supported devices list. I am available for further informations if needed. Kind regards and thank you. Antonello lsusb: Bus 002 Device 003: ID 04e8:3413 Samsung Electronics Co., Ltd SCX-4100 Scanner ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Wed Jul 18 16:21:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1026159/+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 1362640] Re: Remove qtwebkit from touch image
Removing signon-ui. The fix will happen on the signon-plugin-oauth2 project. ** Changed in: signon-ui (Ubuntu) Status: Triaged = Invalid ** Changed in: signon-plugin-oauth2 (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1362640 Title: Remove qtwebkit from touch image Status in the base for Ubuntu mobile products: In Progress Status in Cordova Ubuntu: Fix Released Status in Web Browser App: Triaged Status in signon-plugin-oauth2 package in Ubuntu: In Progress Status in signon-ui package in Ubuntu: Invalid Status in ubuntu-html5-theme package in Ubuntu: In Progress Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Triaged Bug description: The argument to remove this is based on the following: The qtwebkit webview is deprecated for our sdk and we will not be supporting it long term We are supporting an Oxide/Chromium solution for the Ubuntu.Webview This was done largely for security reasons The qtwebkit package is large and we would like to reduce image and install size We want to discourage app devs from using this api any longer, the review tools have indicated this for several months To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362640/+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 1362640] Re: Remove qtwebkit from touch image
** Branch linked: lp:~mardy/signon-plugin-oauth2/lp1362640 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1362640 Title: Remove qtwebkit from touch image Status in the base for Ubuntu mobile products: In Progress Status in Cordova Ubuntu: Fix Released Status in Web Browser App: Triaged Status in signon-plugin-oauth2 package in Ubuntu: In Progress Status in signon-ui package in Ubuntu: Invalid Status in ubuntu-html5-theme package in Ubuntu: In Progress Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Triaged Bug description: The argument to remove this is based on the following: The qtwebkit webview is deprecated for our sdk and we will not be supporting it long term We are supporting an Oxide/Chromium solution for the Ubuntu.Webview This was done largely for security reasons The qtwebkit package is large and we would like to reduce image and install size We want to discourage app devs from using this api any longer, the review tools have indicated this for several months To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362640/+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 1041790]
*** Bug 89671 has been marked as a duplicate of this bug. *** -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in linux package in Ubuntu: Incomplete Status in sandybridge-meta package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash to: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0 run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1361908] [NEW] Brother- DCP7065-DN printer not found
You have been subscribed to a public bug: ubuntu 14.04 LTS Lenovo H53564 bit I had reported, a few weeks ago that this printer was not offered on the sane list. Shortly after an update from ubuntu it did appear on the list was correctly identified and installed working correctly although without the scanner ability not found by any scan program. Recently calling for a print job brings up printer not found or is printer connected a delete and reinstall finds the printer OK but these errors continue. I have disconnected and reconnected printer wires powered off and on but problem remains. Initially I was able to install using the driver for 7085 and will try that again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 26 16:03:53 2014 InstallationDate: Installed on 2014-06-01 (86 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- Brother- DCP7065-DN printer not found https://bugs.launchpad.net/bugs/1361908 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. -- 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 1433945] Re: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1433945 Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lightdm package in Ubuntu: New Bug description: insserv: Starting smfpd depends on ondemand and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: ошибка при обработке пакета lightdm (--configure): подпроцесс установлен сценарий post-installation возвратил код ошибки 1 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 19 10:46:38 2015 DuplicateSignature: package:lightdm:1.12.3-0ubuntu1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-06 (12 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: lightdm Title: package lightdm 1.12.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1433945/+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 1361908] Re: Brother- DCP7065-DN printer not found
Hello David, I switch the package to sane-backends. Are you using USB3? CU Jörg ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New = Incomplete -- 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/1361908 Title: Brother- DCP7065-DN printer not found Status in sane-backends package in Ubuntu: Incomplete Bug description: ubuntu 14.04 LTS Lenovo H53564 bit I had reported, a few weeks ago that this printer was not offered on the sane list. Shortly after an update from ubuntu it did appear on the list was correctly identified and installed working correctly although without the scanner ability not found by any scan program. Recently calling for a print job brings up printer not found or is printer connected a delete and reinstall finds the printer OK but these errors continue. I have disconnected and reconnected printer wires powered off and on but problem remains. Initially I was able to install using the driver for 7085 and will try that again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 26 16:03:53 2014 InstallationDate: Installed on 2014-06-01 (86 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1361908/+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 1298793] Re: Fails to launch in 14.04 (ubuntu-sso-login exited with status 1) (Permission denied: u'/home/.../.cache/sso/sso-client.log')
** Summary changed: - Software Center won't launch 14.04 + Fails to launch in 14.04 (ubuntu-sso-login exited with status 1) (Permission denied: u'/home/.../.cache/sso/sso-client.log') ** Changed in: software-center (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1298793 Title: Fails to launch in 14.04 (ubuntu-sso-login exited with status 1) (Permission denied: u'/home/.../.cache/sso/sso-client.log') Status in software-center package in Ubuntu: Confirmed Bug description: My software center won't launch. I have uninstalled and resintalled several times. I cannot install anything now. WARNING:softwarecenter.db.update:The file: '/usr/share/app-install/desktop/sonic-visualiser:x-sonicvisualiser-layer.desktop' could not be read correctly. The application associated with this file will not be included in the software catalog. Please consider raising a bug report for this issue with the maintainer of that application WARNING:softwarecenter.db.update:The file: '/usr/share/app-install/desktop/sonic-visualiser:x-sonicvisualiser.desktop' could not be read correctly. The application associated with this file will not be included in the software catalog. Please consider raising a bug report for this issue with the maintainer of that application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1298793/+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 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
Rolf: targetting trusty is fine, it will be redirected to -proposed automatically. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) Status in The GNOME 2 Session Manager: Fix Released Status in gnome-session package in Ubuntu: Triaged Status in gnome-session source package in Trusty: New Status in gnome-session source package in Utopic: New Status in gnome-session source package in Vivid: Triaged Status in gnome-session package in Debian: New Bug description: This bug will cause static grey or black screen instead of openning remote session using Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting from x2goclient, rdpclient(reminna/vinagre/mstsc), SSH, VNC, NOMACHINE and etc. 1) lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 2) apt-cache policy gnome-session gnome-session: Installed: 3.9.90-0ubuntu12 Candidate: 3.9.90-0ubuntu12 Version table: *** 3.9.90-0ubuntu12 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy gnome-session-fallback gnome-session-fallback: Installed: 1:3.8.0-1ubuntu12.1 Candidate: 1:3.8.0-1ubuntu12.1 Version table: *** 1:3.8.0-1ubuntu12.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 100 /var/lib/dpkg/status 1:3.8.0-1ubuntu11 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages apt-cache policy xrdp xrdp: Installed: 0.6.0-1 Candidate: 0.6.0-1 Version table: *** 0.6.0-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status apt-cache policy remmina remmina: Installed: 1.0.0-4ubuntu3 Candidate: 1.0.0-4ubuntu3 Version table: *** 1.0.0-4ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy vinagre vinagre: Installed: 3.10.2-0ubuntu1 Candidate: 3.10.2-0ubuntu1 Version table: *** 3.10.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one installs xrdp on the host and attempts to use remmina or vinagre on a Ubuntu 14.04 client to RDP in, it works. 4) What happens instead is it shows a gray static screen as per attached screenshot. This would appear an issue with gnome-session as per client log: cat .xsession-errors.old Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. init: indicator-application main process ended, respawning init: indicator-application main process ended, respawning init: indicator-application respawning too fast, stopped Xsession: X session started for at Sun Jul 20 15:25:59 CDT 2014 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:moniker being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 ** (process:2565): WARNING **: software acceleration check failed: Child process exited with code 1 ** (x-session-manager:2565): CRITICAL **: We failed, but the fail whale is dead. Sorry The following is not a WORKAROUND, create /etc/xorg.conf : Section Device Identifier Intel Graphics Driver Intel Option DRI False EndSection ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session 3.9.90-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 15:35:23 2014 InstallationDate: Installed on 2014-06-22 (28 days
[Desktop-packages] [Bug 1405380] Re: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale()
Thanks, that seems similar to https://bugzilla.gnome.org/show_bug.cgi?id=740958 ... maybe you could comment on the upstream bug mentioned your similar issue? ** Bug watch added: GNOME Bug Tracker #740958 https://bugzilla.gnome.org/show_bug.cgi?id=740958 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1405380 Title: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale() Status in evince package in Ubuntu: Confirmed Bug description: Evince crashed after about 10 minutes printing to file PDF with the attached. The next time I printed it took 2 hours so it is intermittenly reproducible. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 24 01:00:32 2014 ExecutablePath: /usr/bin/evince ExecutableTimestamp: 1413470384 InstallationDate: Installed on 2014-12-14 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141213) ProcCmdline: evince /home/name/Desktop/grammar4.ps ProcCwd: /home/name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8734828a08 INT_cairo_surface_set_device_scale+8: mov0x1c(%rdi),%r9d PC (0x7f8734828a08) ok source 0x1c(%rdi) (0x001c) not located in a known VMA region (needed readable region)! destination %r9d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: INT_cairo_surface_set_device_scale (surface=0x0, sx=1, sy=1) at /build/buildd/cairo-1.13.0~20140204/src/cairo-surface.c:1676 set_device_scale_on_surface (device_scale=optimized out, surface=optimized out) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:273 copy_job_to_job_info (job_render=job_render@entry=0x1a27010, job_info=job_info@entry=0x154df00, pixbuf_cache=pixbuf_cache@entry=0x1427340) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:288 job_finished_cb (job=optimized out, pixbuf_cache=0x1427340) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:340 _g_closure_invoke_va (closure=0x0, closure@entry=0x19187d0, return_value=return_value@entry=0x0, instance=0x0, instance@entry=0x1a27010, args=0x7f8714021c30, args@entry=0x7fff7e9903d0, n_params=0, param_types=0x7f8714021760) at /build/buildd/glib2.0-2.43.2/./gobject/gclosure.c:831 Title: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1405380/+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 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Description changed: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver-xorg-video-ati. But there are new versions available (xserver-xorg-video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic - removed both old packages and Xorg doesn't work after that. I selected + removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': - . Exiting. - Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE - Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. - Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. - Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. - Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... - Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. - Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt - Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. - Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. - Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address - Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 - Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made - Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. - Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE - Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. - Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. - Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. - Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... - Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. - Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt - Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. - Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. - Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address - Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 - Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made - Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) + . Exiting. + Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE + Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. + Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. + Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. + Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... + Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. + Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt + Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. + Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. + Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address + Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 + Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made + Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
[Desktop-packages] [Bug 1380996] Re: File size for backups not user-defineable
** Branch linked: lp:~beowulfof/+junk/deja-dup -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1380996 Title: File size for backups not user-defineable Status in deja-dup package in Ubuntu: New Bug description: Description: Ubuntu 14.04.1 LTS Release: 14.04 deja-dup: Installiert: 30.0-0ubuntu4 Installationskandidat: 30.0-0ubuntu4 Versionstabelle: *** 30.0-0ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Deja-Dup still has file size for backups hard-coded?!? but not user-defined. It is allways good to have a standard that fits for most user, but the ability to define custom sizes for file size in backup without having to rewrite the whole program would be nice. Please make the filesize for the backups an option in settings tab. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-38.65-generic 3.13.11.8 Uname: Linux 3.13.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 14 12:05:01 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-25 (353 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2014-04-22 (174 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1380996/+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 1434049] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1431041 *** https://bugs.launchpad.net/bugs/1431041 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1431041, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1434049/+attachment/4349852/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1434049/+attachment/4349855/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1434049/+attachment/4349862/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1434049/+attachment/4349864/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1434049/+attachment/4349865/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1434049/+attachment/4349866/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1434049/+attachment/4349867/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1431041 cups-browsed crashed with SIGSEGV in timeout_free() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1434049 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() Status in cups-filters package in Ubuntu: New Bug description: init session ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 CupsErrorLog: Date: Wed Mar 18 13:44:53 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-01-31 (46 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150130) Lpstat: device for Generic-CUPS-PDF-Printer: cups-pdf:/ MachineType: ASUSTeK COMPUTER INC. S301LA Papersize: a4 PpdFiles: Generic-CUPS-PDF-Printer: Generic CUPS-PDF Printer ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=es_BO.UTF-8 LANGUAGE=es_BO:es PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed root=UUID=12dfe53e-d52f-40fb-9fa8-1b0bf515eeac ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f82e2f9715a:movl $0x1,0xa8(%rax) PC (0x7f82e2f9715a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S301LA.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S301LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS301LA.205:bd08/19/2013:svnASUSTeKCOMPUTERINC.:pnS301LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS301LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S301LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1434049/+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 1434061] [NEW] Icon of nautilus marked with arrow instead of reсycle bin
Public bug reported: When opened window of recycle bin icon of nautilus marked with arrow as through i open window of nautilus, but if want see that window, and click on icon of nautilus - i new window of nautilus. And if i have many opened windows, i can find that window (of recycle bin) only with ALT+TAB. Such behavior is not logical. If i see icon checked with arrow, it means that there is already opened window, and i can click on icon to see that window instead of new window of naulitus. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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 CurrentDesktop: Unity Date: Thu Mar 19 22:22:47 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3555] InstallationDate: Installed on 2014-10-04 (166 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=e7ddd973-00c9-490f-a98d-95ebd78f4dfb ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Mar 9 14:55:33 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech G400s Optical Gaming Mouse MOUSE, id 8 inputEee PC WMI hotkeys KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1434061 Title: Icon of nautilus marked with arrow instead of reсycle bin Status in unity package in Ubuntu: New Bug description: When opened window of recycle bin icon of nautilus marked with arrow as through i open window of nautilus, but if want see that window, and click on icon of nautilus - i new window of nautilus. And if i have many opened windows, i can find that window (of recycle bin) only with ALT+TAB. Such behavior is not logical. If i see icon checked with arrow, it means that there is already opened window, and i can click on icon to see that window instead of new window of
[Desktop-packages] [Bug 1434036] [NEW] ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
You have been subscribed to a public bug: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver-xorg-video-ati. But there are new versions available (xserver-xorg-video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg doesn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us. Thanks in advance. Cheers, Christian ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: black blink cursor radeon screen -- ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update https://bugs.launchpad.net/bugs/1434036 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. -- 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 1405380] Re: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale()
Sebastien Bacher, thanks for the follow up. Given the offending file is attached to this report, I'll print a few times with the latest version of Evince in Vivid (3.14.2-0ubuntu1), and if reproducible I'll just file a new report upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1405380 Title: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale() Status in evince package in Ubuntu: Confirmed Bug description: Evince crashed after about 10 minutes printing to file PDF with the attached. The next time I printed it took 2 hours so it is intermittenly reproducible. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 24 01:00:32 2014 ExecutablePath: /usr/bin/evince ExecutableTimestamp: 1413470384 InstallationDate: Installed on 2014-12-14 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141213) ProcCmdline: evince /home/name/Desktop/grammar4.ps ProcCwd: /home/name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8734828a08 INT_cairo_surface_set_device_scale+8: mov0x1c(%rdi),%r9d PC (0x7f8734828a08) ok source 0x1c(%rdi) (0x001c) not located in a known VMA region (needed readable region)! destination %r9d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: INT_cairo_surface_set_device_scale (surface=0x0, sx=1, sy=1) at /build/buildd/cairo-1.13.0~20140204/src/cairo-surface.c:1676 set_device_scale_on_surface (device_scale=optimized out, surface=optimized out) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:273 copy_job_to_job_info (job_render=job_render@entry=0x1a27010, job_info=job_info@entry=0x154df00, pixbuf_cache=pixbuf_cache@entry=0x1427340) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:288 job_finished_cb (job=optimized out, pixbuf_cache=0x1427340) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:340 _g_closure_invoke_va (closure=0x0, closure@entry=0x19187d0, return_value=return_value@entry=0x0, instance=0x0, instance@entry=0x1a27010, args=0x7f8714021c30, args@entry=0x7fff7e9903d0, n_params=0, param_types=0x7f8714021760) at /build/buildd/glib2.0-2.43.2/./gobject/gclosure.c:831 Title: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1405380/+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
Re: [Desktop-packages] [Bug 1029410] Re: 2 scanners, 1 not visible to user, only root can see it
On Thursday 19 March 2015 05:59:04 Jörg Frings-Fürst wrote: Hello Gene, I set the package to sane-backends. can you tell me whats your changes at udev/rules.d? Not at this late date as I have now installed a wheezy derivative in amd64 flavor from the linuxcnc.org site. And that old epson scanner has been retired recycled to boot, so I am down to one scanner, and I can see it and use it as user #1. Root can see it, but can't use it because root cannot open a window on my 0:0 display. That is a PIMA but thats how it works these days, so I have to use something like nano to edit root's crap. Sorry I can't help at this time. Thanks Jörg ** Package changed: sane-frontends (Ubuntu) = sane-backends (Ubuntu) ** Changed in: sane-backends (Ubuntu) Status: New = Incomplete Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene -- 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/1029410 Title: 2 scanners, 1 not visible to user, only root can see it Status in sane-backends package in Ubuntu: Incomplete Bug description: I am not sure what to shake a finger at, but I fixed it with a udev file not supplied by ubuntu ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: sane 1.0.14-9 ProcVersionSignature: Ubuntu 2.6.32-122.35.rtai-rtai 2.6.32.11+drm33.2 Uname: Linux 2.6.32-122-rtai i686 Architecture: i386 Date: Thu Jul 26 07:53:10 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: sane-frontends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1029410/+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 1434036] [NEW] ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
Public bug reported: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver-xorg-video-ati. But there are new versions available (xserver-xorg-video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg doesn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us. Thanks in advance. Cheers, Christian ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: black blink cursor radeon screen ** Package changed: nux (Ubuntu) = xserver-xorg-video-ati (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
This bug was fixed in the package fglrx-installer-updates - 2:15.200-0ubuntu2 --- fglrx-installer-updates (2:15.200-0ubuntu2) vivid; urgency=medium * debian/control.in: - Provide opencl-icd (LP: #1129409). -- Alberto Milone alberto.mil...@canonical.com Thu, 19 Mar 2015 12:34:49 +0100 ** Changed in: fglrx-installer-updates (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1433198] Re: 15.04 daily images don't reach X using VirtualBox - VESA error: Cannot read int vect
This bug was fixed in the package xorg-server - 2:1.17.1-0ubuntu3 --- xorg-server (2:1.17.1-0ubuntu3) vivid; urgency=medium * Add a patch to fix vesa int10 failure. (LP: #1433198) -- Maarten Lankhorst maarten.lankho...@ubuntu.com Thu, 19 Mar 2015 10:13:08 +0100 ** Changed in: xorg-server (Ubuntu) Status: Confirmed = Fix Released -- 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/1433198 Title: 15.04 daily images don't reach X using VirtualBox - VESA error: Cannot read int vect Status in xorg-server package in Ubuntu: Fix Released Bug description: Trying the Ubuntu MATE 15.04 daily images (i386 and amd64) from 17th March 2016, they are unable to reach X. Logs coming... --- ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CasperVersion: 1.352 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu-MATE 15.04 Vivid Vervet - Alpha i386 (20150317) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: xorg-server (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Tags: vivid ubuntu regression reproducible UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-9-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Mar 17 16:16:18 2015 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1433198/+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 1432843] Re: Lubuntu failed to boot
Here a pic of the output in nomodeset when the installation on disk does not progress (daily 20150318 i386). ** Attachment added: IMGP3891.jpg https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4349792/+files/IMGP3891.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432843 Title: Lubuntu failed to boot Status in xorg package in Ubuntu: Confirmed Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
This bug was fixed in the package fglrx-installer - 2:15.200-0ubuntu2 --- fglrx-installer (2:15.200-0ubuntu2) vivid; urgency=medium * debian/control.in: - Provide opencl-icd (LP: #1129409). -- Alberto Milone alberto.mil...@canonical.com Thu, 19 Mar 2015 12:25:58 +0100 ** Changed in: fglrx-installer (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in boinc source package in Trusty: Invalid Status in fglrx-installer source package in Trusty: Confirmed Status in fglrx-installer-updates source package in Trusty: Confirmed Status in nvidia-cuda-toolkit source package in Trusty: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Invalid Status in nvidia-graphics-drivers-304-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-310-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-313-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-319 source package in Trusty: Invalid Status in nvidia-graphics-drivers-319-updates source package in Trusty: Invalid Status in nvidia-graphics-drivers-340 source package in Trusty: Invalid Status in pycuda source package in Trusty: Invalid Status in pyopencl source package in Trusty: Invalid Status in starpu-contrib source package in Trusty: Invalid Status in viennacl source package in Trusty: Invalid Status in boinc source package in Utopic: Invalid Status in fglrx-installer source package in Utopic: Confirmed Status in fglrx-installer-updates source package in Utopic: Confirmed Status in nvidia-cuda-toolkit source package in Utopic: Invalid Status in nvidia-graphics-drivers-304 source package in Utopic: Invalid Status in nvidia-graphics-drivers-304-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-310-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-313-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-319 source package in Utopic: Invalid Status in nvidia-graphics-drivers-319-updates source package in Utopic: Invalid Status in nvidia-graphics-drivers-340 source package in Utopic: Invalid Status in pycuda source package in Utopic: Invalid Status in pyopencl source package in Utopic: Invalid Status in starpu-contrib source package in Utopic: Invalid Status in viennacl source package in Utopic: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1434030] [NEW] [HDA-Intel - HDA Intel, playback] No sound at all
Public bug reported: Digital Output (SPDIF) Built-in Audio. No sound at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prestley 1493 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 19 16:24:34 2015 InstallationDate: Installed on 2007-01-01 (2999 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prestley 1493 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: PI945GCM dmi.board.vendor: Kobian dmi.board.version: ECS dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd05/08/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: PI945GCM dmi.product.version: 1.X dmi.sys.vendor: Kobian ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1434030 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: Digital Output (SPDIF) Built-in Audio. No sound at all. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prestley 1493 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 19 16:24:34 2015 InstallationDate: Installed on 2007-01-01 (2999 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prestley 1493 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: PI945GCM dmi.board.vendor: Kobian dmi.board.version: ECS dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd05/08/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: PI945GCM dmi.product.version: 1.X dmi.sys.vendor: Kobian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1434030/+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 1405380] Re: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale()
I can confirm the issue in vivid, no need to print, just browsing the document is enough -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1405380 Title: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale() Status in evince package in Ubuntu: Confirmed Bug description: Evince crashed after about 10 minutes printing to file PDF with the attached. The next time I printed it took 2 hours so it is intermittenly reproducible. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 24 01:00:32 2014 ExecutablePath: /usr/bin/evince ExecutableTimestamp: 1413470384 InstallationDate: Installed on 2014-12-14 (10 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141213) ProcCmdline: evince /home/name/Desktop/grammar4.ps ProcCwd: /home/name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8734828a08 INT_cairo_surface_set_device_scale+8: mov0x1c(%rdi),%r9d PC (0x7f8734828a08) ok source 0x1c(%rdi) (0x001c) not located in a known VMA region (needed readable region)! destination %r9d ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: INT_cairo_surface_set_device_scale (surface=0x0, sx=1, sy=1) at /build/buildd/cairo-1.13.0~20140204/src/cairo-surface.c:1676 set_device_scale_on_surface (device_scale=optimized out, surface=optimized out) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:273 copy_job_to_job_info (job_render=job_render@entry=0x1a27010, job_info=job_info@entry=0x154df00, pixbuf_cache=pixbuf_cache@entry=0x1427340) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:288 job_finished_cb (job=optimized out, pixbuf_cache=0x1427340) at /build/buildd/evince-3.14.1/./libview/ev-pixbuf-cache.c:340 _g_closure_invoke_va (closure=0x0, closure@entry=0x19187d0, return_value=return_value@entry=0x0, instance=0x0, instance@entry=0x1a27010, args=0x7f8714021c30, args@entry=0x7fff7e9903d0, n_params=0, param_types=0x7f8714021760) at /build/buildd/glib2.0-2.43.2/./gobject/gclosure.c:831 Title: evince crashed with SIGSEGV in INT_cairo_surface_set_device_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1405380/+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 1434341] [NEW] Intel HD5500: No video after suspend/resume cycle
Public bug reported: Thinkpad T550, Vivid Suspend/resume works sometimes. On restore, no image on X. System apparently still active, because keyboard light (e.g. mute) still responding. Could not switch to console using ctrl-alt-f1. Thinkpad T550, Trusty Suspend/resume worked almost every time for 2 weeks. light-locker seems to screw things up by changing video modes, so I always remove that. Suspend/resume/lock/etc always fails with light-locker. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 18:41:36 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1434341 Title: Intel HD5500: No video after suspend/resume cycle Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Thinkpad T550, Vivid Suspend/resume works sometimes. On restore, no image on X. System apparently still active, because keyboard light (e.g. mute) still responding. Could not switch to console using ctrl-alt-f1. Thinkpad T550, Trusty Suspend/resume worked almost every time for 2 weeks. light-locker seems to screw things up by changing video modes, so I always remove that. Suspend/resume/lock/etc always fails with light-locker. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 18:41:36 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1434341/+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 1434351] [NEW] X fonts and widgets disappear after suspend/resume cycle
Public bug reported: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: Screenshot of problem https://bugs.launchpad.net/bugs/1434351/+attachment/4350446/+files/xubuntu-intel-bad-video-2015-03-19_19-36-45.png -- 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/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1434351/+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 1290051] Re: avconv crashed with SIGSEGV in malloc_consolidate()
[Expired for libav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libav (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1290051 Title: avconv crashed with SIGSEGV in malloc_consolidate() Status in libav package in Ubuntu: Expired Bug description: avconv has crashed. $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy libav-tools libav-tools: Installed: 6:9.11-2ubuntu1 Candidate: 6:9.11-2ubuntu1 Version table: *** 6:9.11-2ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libav-tools 6:9.11-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 9 10:59:27 2014 ExecutablePath: /usr/bin/avconv InstallationDate: Installed on 2013-12-28 (71 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131219) ProcCmdline: avconv -i 2014-03-08,\ Cultural\ Program\ at\ Home\ with\ Grandma.mp4 -threads 4 -s hd480 -vb 2048k -deadline best -f webm 2014-03-08,\ Cultural\ Program\ at\ Home\ with\ Grandma.mp4.webm SegvAnalysis: Segfault happened at: 0x7fc6523334d5 malloc_consolidate+133: cmp 0x18(%rax),%r12 PC (0x7fc6523334d5) ok source 0x18(%rax) (0xdfd71a44a5d4f6c1) not located in a known VMA region (needed readable region)! destination %r12 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libav StacktraceTop: malloc_consolidate (av=av@entry=0x7fc652673760 main_arena) at malloc.c:4165 _int_malloc (av=0x7fc652673760 main_arena, bytes=9296) at malloc.c:3423 _int_memalign (av=0x7fc652673760 main_arena, alignment=32, bytes=1459817819648927439, bytes@entry=9216) at malloc.c:4403 _mid_memalign (alignment=32, bytes=9216, address=optimized out) at malloc.c:3106 __posix_memalign (memptr=0x7fff4ec57cf8, alignment=18446744073709551615, size=140734514952320) at malloc.c:5016 Title: avconv crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1290051/+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 632034] Re: pppd: unrecognized option 'lock'
[Expired for ppp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ppp (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/632034 Title: pppd: unrecognized option 'lock' Status in ppp package in Ubuntu: Expired Bug description: Binary package hint: ppp Description:Ubuntu 10.04.1 LTS Release:10.04 Linux unlin 2.6.32-25-generic #43-Ubuntu SMP Wed Sep 1 09:46:13 UTC 2010 x86_64 GNU/Linux Installed: 2.4.5~git20081126t100229-0ubuntu3 Candidate: 2.4.5~git20081126t100229-0ubuntu3 Version table: *** 2.4.5~git20081126t100229-0ubuntu3 0 500 http://mirror.yandex.ru/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status My DSL connection fails to start because of network-manager call pppd with lock option. Here is a command that network-manager uses to connect: /usr/sbin/pppd nodetach lock nodefaultroute user l...@domain.net plugin rp-pppoe.so nic-eth0 noauth refuse-eap refuse-chap refuse- mschap refuse-mschap-v2 nobsdcomp nodeflate usepeerdns mru 1492 mtu 1492 lcp-echo-failure 5 lcp-echo-interval 30 ipparam /org/freedesktop/NetworkManager/PPP/6 plugin /usr/lib/pppd/2.4.4/nm- pppd-plugin.so It looks like pppd does not configured with lock support. According to man pppd: lock Specifies that pppd should create a UUCP-style lock file for the serial device to ensure exclusive access to the device. By default, pppd will not create a lock file. I think pppd should support this option. Please let me know if you need additional info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/632034/+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 940721] Re: ffmpeg goes berserk when trying to convert this video to mjpeg
[Expired for libav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libav (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/940721 Title: ffmpeg goes berserk when trying to convert this video to mjpeg Status in libav package in Ubuntu: Expired Bug description: I have a 3gp video of 20 seconds, 10 fps, 480x640 resolution, h264 codec, for a file size of about 4 MB; I tried the following command: ffmpeg -i VIDEO0024.3gp -vcodec mjpeg -s 300x400 -qmin 0.8 -qmax 0.8 VIDEO0024.mov After several minutes, ffmpeg had processed more than 145357 frames, reported a time of 1.62 seconds, had written more than one GIGABYTE of output and was still working. I obviously killed it. The exactly same command has worked just fine with other video files encoded with other codecs. I think the problem is that for some reason it by default uses an output framerate of about 9 fps. Adding -r 10 for the output fixes the issue. But it is still an issue: according to documentation the default framerate is 30fps, anyway 9 is certainly not a reasonable default. I erroneously reported this in the FFmpeg bugtracker and they say it's probably fixed in FFmpeg. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: ffmpeg 4:0.7.3-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Feb 25 01:49:11 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libav UpgradeStatus: Upgraded to oneiric on 2011-12-07 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/940721/+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 1308607] Re: avconv uses only 1 core Ubuntu 13.10
[Expired for libav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libav (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1308607 Title: avconv uses only 1 core Ubuntu 13.10 Status in libav package in Ubuntu: Expired Bug description: I tried to get a movie transcoded with libx264 and libvorbis instead of AC3-DTS but avconv is not using all 4 cores of my computer. The original file has the video track plus three audio tracks, one in DTS- HD MA, one in DTS and the last one in AC3. My command line is this: avconv -i MOVIE.mkv -map 0:0 -codec:v libx264 -pass 1 -threads 6 -coder:v ac -g 240 -keyint_min 23 -bf:v 16 -b_strategy 2 -b-bias 0 -refs 3 -b:v 11000k -partitions p8x8,b8x8,i8x8,i4x4 -mixed-refs 1 -me_range:v 20 -me_method:v umh -subq 8 -b-pyramid strict -8x8dct 1 -direct-pred 1 -weightb 1 -weightp 2 -deblock 0:0 -an -f rawvideo -y /dev/null ; avconv -i MOVIE.mkv -map 0 -map -0:2 -map -0:3 -codec:s copy -codec:v libx264 -pass 2 -threads 6 -coder:v ac -g 240 -keyint_min 23 -bf:v 16 -b_strategy 2 -b-bias 0 -refs 3 -b:v 11000k -partitions p8x8,b8x8,i8x8,i4x4 -mixed-refs 1 -me_range:v 20 -me_method:v umh -subq 8 -b-pyramid strict -8x8dct 1 -direct-pred 1 -weightb 1 -weightp 2 -deblock 0:0 -acodec libvorbis -async 1 -b:a:0 640k -metadata:s:a:0 title=arc Vorbis 640k 5.1 OUTPUT-MOVIE.mkv I tried to do a 1 pass encode with the second pass command (without the -pass 2 option) for testing purposes and it didn't use more than 1 core (total load of avconv remained ~130%, I assume it's 100% of libx264 plus some processing for the audio). At times it went up near 400% but it never didn't stay at full load, most of the time (99% of the time) was spent on ~130%. I've also tried with -threads auto, -threads 0, -threads 4 but no luck. I'm using the avconv available in Ubuntu 13.10 repositories (I'm on Kubuntu 13.10): 6:0.8.10-0ubuntu0.13.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1308607/+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 1334291] Re: package libswscale-extra-2 (not installed) failed to install/upgrade: libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not co-installable with li
[Expired for libav (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libav (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1334291 Title: package libswscale-extra-2 (not installed) failed to install/upgrade: libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not co-installable with libswscale-extra-2 which has multiple installed instances Status in libav package in Ubuntu: Expired Bug description: i do not undestand ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libswscale-extra-2 (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 AptOrdering: libswscale-extra-2: Install libswscale-extra-2: Configure libavfilter-extra-2: Configure Architecture: amd64 Date: Sat Jun 21 10:32:40 2014 DpkgHistoryLog: Start-Date: 2014-06-21 10:32:39 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.79' Install: libswscale-extra-2:amd64 (9.13-0ubuntu0.14.04.1, automatic) DpkgTerminalLog: dpkg: error processing archive /var/cache/apt/archives/libswscale-extra-2_6%3a9.13-0ubuntu0.14.04.1_all.deb (--unpack): libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not co-installable with libswscale-extra-2 which has multiple installed instances DuplicateSignature: package:libswscale-extra-2:(not installed):libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not co-installable with libswscale-extra-2 which has multiple installed instances ErrorMessage: libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not co-installable with libswscale-extra-2 which has multiple installed instances InstallationDate: Installed on 2013-05-24 (397 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: libav Title: package libswscale-extra-2 (not installed) failed to install/upgrade: libswscale-extra-2:all 6:9.13-0ubuntu0.14.04.1 (Multi-Arch: no) is not co-installable with libswscale-extra-2 which has multiple installed instances UpgradeStatus: Upgraded to trusty on 2014-05-01 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1334291/+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 1411890] Re: nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build
[Expired for nvidia-graphics-drivers-331 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1411890 Title: nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: Expired Bug description: When installing linux-headers from kernel.ubuntu.com, an error raised. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.113-0ubuntu0.1 [modified: usr/src/nvidia-331-331.113/dkms.conf] Uname: Linux 3.18.1-031801-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 DKMSKernelVersion: 3.18.3-031803-generic Date: Sat Jan 17 10:21:49 2015 InstallationDate: Installed on 2014-10-11 (97 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.1: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-16 (92 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1411890/+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 1416891] Re: Update to 1.20.3
I installed the update from -proposed a few days ago and did not spot any immediately obvious regressions. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1416891 Title: Update to 1.20.3 Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Trusty: Fix Committed Bug description: [Impact] Ubuntu 14.04 LTS currently contains 1.20.1. There have been stable updates since then. The maintainer has requested we update [1]. [Test Case] Update to 1.20.3. Still should keep working as before. [Regression Potential] Some risk of other bugs being created by changes. Code inspection shows changes are relatively simple. [1] https://lists.ubuntu.com/archives/ubuntu- devel/2015-February/038668.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1416891/+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