[Desktop-packages] [Bug 1237904] Re: Xorg crashed with SIGABRT in OsAbort()
** Also affects: ubuntu-gnome Importance: Undecided Status: New ** Changed in: ubuntu-gnome Milestone: None => wily -- 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/1237904 Title: Xorg crashed with SIGABRT in OsAbort() Status in Ubuntu GNOME: New Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Bug description: [Impact] This crash is ranking #2 on errors.u.c[1], it is caused by a recursive call to xf86CloseConsole() after a failed VT switch. Since it is happening on shutdown, its not causing any real issues with the user session, however it is spamming the users (and errors.u.c) with crash logs. [Test Case] 1. Running under a gdm/gnome-shell session select 'power off' from the user menu (it doesn't get triggered on a restart) 2. On next login you will receive a crash report [Regression Potential] Very Low, its an upstream patch, that just changes the error logging, so that the a warning is logged rather than crashing the server. [1] https://errors.ubuntu.com/problem/27941445d596fb71be692b9008c0847d2ce6c428 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1237904/+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 1510970] Re: Intel driver crashes on Ubuntu 15.10
Disabling animations did not help me. There are less crashes but still happens. Almost everytime when I try to reply to a mail or open calendar event in Thunderbird. This is not happening on other machines with non- intel graphic cards. -- 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/1510970 Title: Intel driver crashes on Ubuntu 15.10 Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before the update everything was stable. The problem occured mostly while using Thunderbird but also once while using Firefox. The Xserver crashes and I'm logged out. It takes about 10 seconds until gdm fires up again and I'm able to login again. The last part of /var/log/Xorg.0.log says: [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920 [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (0, 0), rotation left, reflection none [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1080, 406), rotation normal, reflection none [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1080, 502), rotation normal, reflection none [ 20012.432] (EE) [ 20012.432] (EE) Backtrace: [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e] [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999] [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) [0x7fe7c65522f0] [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18] [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x26157) [0x7fe7c291a157] [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1] [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4] [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c] [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a] [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x4197c) [0x7fe7c293597c] [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x59906) [0x7fe7c294d906] [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654] [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274] [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502] [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a] [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5] [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f] [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b] [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fe7c653da40] [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9] [ 20012.433] (EE) [ 20012.433] (EE) Segmentation fault at address 0x0 [ 20012.433] (EE) Fatal server error: [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 20012.433] (EE) [ 20012.433] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 20012.433] (EE) [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch [ 20012.456] (EE) Server terminated with error (1). Closing log file. These parts of dmesg might be interesting: [1.661760] input: Logitech USB Keyboard as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8 [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1 [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder B [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [2.586624] clocksource: Switched to clocksource tsc [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not implemented [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +S
[Desktop-packages] [Bug 1283426] Re: nautilus crashed with SIGSEGV in build_file_list_from_uris()
** Changed in: nautilus Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1283426 Title: nautilus crashed with SIGSEGV in build_file_list_from_uris() Status in Nautilus: Invalid Status in gtk+3.0 package in Ubuntu: Fix Committed Bug description: I was trying to copy a file out of a VMware Player virtual Windows 7 guest runnning in a window to nautilus, drag-and-dropping. The reverse operation (From nautilus to virtual machine's desktop) is executed fine. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 22 13:16:46 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2014-02-15 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140214) ProcCmdline: nautilus -n SegvAnalysis: Segfault happened at: 0x7f36910aa0b9:mov(%rdi),%rdi PC (0x7f36910aa0b9) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1283426/+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 1511674] Re: Memory leak
Thank you very much. It works! Is there any chance to backport this fix to LTS version of Ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1511674 Title: Memory leak Status in pcsc-lite package in Ubuntu: New Bug description: I noticed that pcscd consumes a lot of memory (5GB after 48h since start) in one of my computers (ubuntu 14.04 64-bit pcsc-lite version 1.8.10.) In debug mode pcscd shows a lot of USB "device removed" notifications: 0102 hotplug_libudev.c:594:HPEstablishUSBNotifications() Device removed 1297 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 [cut - long list of usb devices] 0246 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x03EB, PID: 0x2044, path: /dev/bus/usb/001/067 00022327 winscard_svc.c:319:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 00500329 winscard_svc.c:319:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 00500341 winscard_svc.c:319:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 Flood of "device removed" messages was caused by some broken USB device (not card reader - CDC-ACM device), but it doesn't explain why pcscd allocated 5GB of memory. Is it some memory leak in pcscd? lsb_release -rd: Description: Ubuntu 14.04.3 LTS Release: 14.04 pcscd: Installed: 1.8.10-1ubuntu1 Candidate: 1.8.10-1ubuntu1 Version table: *** 1.8.10-1ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1511674/+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 995847] Re: nautilus needs manual refresh to show changes in cifs mounted folders
** Changed in: nautilus Status: New => Confirmed -- 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/995847 Title: nautilus needs manual refresh to show changes in cifs mounted folders Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: If the nautilus window shows files from network folders mounted with cifs, changes in this files are mostly not shown until a manual refresh (F5). For Example if I type "touch test" in the terminal the new file is not shown until I refresh with F5. But after "rm test" the change is shown. Changes from other users over the network are never shown without explicit refresh. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Mon May 7 10:45:00 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+236+118' InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/995847/+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 1511974] Re: Touchpad Not Working
** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1511974 Title: Touchpad Not Working Status in xorg package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 14 to 15.10 the touchpad no longer works. To get it to work, I must manually reload the mouse drivers through terminal. However, this only works for the current session. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 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 Date: Sat Oct 31 09:33:20 2015 DistUpgraded: 2015-10-30 19:09:33,409 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 4.2.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0360] InstallationDate: Installed on 2015-10-30 (1 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Acer Aspire 5553G ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic root=UUID=54ee2d2f-fb32-4d3c-b506-16f0dcbc6d52 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.23 dmi.board.name: JV51_DN dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.23:bd04/25/2011:svnAcer:pnAspire5553G:pvrNotApplicable:rvnAcer:rnJV51_DN:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5553G dmi.product.version: Not Applicable dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 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: Fri Oct 30 21:28:01 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511974/+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 1197870] Re: debian-changelog-mode support for non-coreutils systems
** Changed in: emacs-goodies-el Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs-goodies-el in Ubuntu. https://bugs.launchpad.net/bugs/1197870 Title: debian-changelog-mode support for non-coreutils systems Status in emacs-goodies: New Status in emacs-goodies-el package in Ubuntu: Confirmed Bug description: The current debian-changelog-mode shells out to coreutils' date. To increase portability (some developers work on packages from other architectures), it would be nice to see this clean up get integrated: https://github.com/pcarrier/debian-changelog-mode/commit/fcf691df I get this should be reported upstream, but I won't pursue this further. Feel free to report/champion if this is of any interest to you. To manage notifications about this bug go to: https://bugs.launchpad.net/emacs-goodies-el/+bug/1197870/+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 1506696] Re: Bullets and numbering ignores paragraph formatting
This bug is for Libre Office, not Open Office. Sorry, I forgot (been using OO and LO since 1999). Please change the report to LO. I'm using Ubuntu 14.04, up to date. On 10/17/2015 01:43 PM, Christopher M. Penalver wrote: > octalman, thank you for reporting this and helping make Ubuntu. > > However, there are no new official Apache OpenOffice/OpenOffice.org > releases in Ubuntu, as the Ubuntu project has transitioned to > LibreOffice. Hence, the status of this report is being marked as Won't > Fix. > > You are welcome to test for this problem in LibreOffice. If reproducible, > please click the button: > Also affects distribution > > Distribution: Ubuntu > Source Package Name: (Optional) libreoffice > > For more on installing LibreOffice please see > https://wiki.ubuntu.com/LibreOffice. > > Thank you for your understanding. > > ** Changed in: openoffice.org (Ubuntu) > Status: New => Won't Fix > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openoffice.org in Ubuntu. https://bugs.launchpad.net/bugs/1506696 Title: Bullets and numbering ignores paragraph formatting Status in openoffice.org package in Ubuntu: Won't Fix Bug description: After years of fighting OO Writer's bullets and numbering, I have finally discovered at least part of the problem. It appears to consist of two parts. 1. There is no "No, I don't want bullets and numbering" for a selected paragraph. Both the formatting drop-down/paragraph and the bullent-and-numbering drop-down should both have this option, explicitly. More specifically, 2. Bullets and numbering is ultra aggressive. Under some conditions, even when bullets and numbering is turned off for a paragraph, O-O tries to implement numbering anyway. Worse, when this happens, not only the current paragraph is infected, but one or more subsequent paragraphs will also be affected, and the problem cannot be fixed. Bullets and numbering energizes itself, even if the paragraph does not have bullets and numbering enabled, when one or more of the following occur: .. A paragraph begins with a capital letter immediately followed by a period .. A paragraph begins with certain capital letters (C, but apparently others as well) .. The first character of the paragraph is a numeral followed by a period This issue with respect to the second item above can be overcome by enclosing the offending letter and some following text in double quotes (U S style, "). I don't know whether this works for numerals, however, or if only the first letter is so enclosed. Under these circumstances, it is impossible to disable bullets and numbering. When this aggressive behaviour occurs, it also causes indentation specifications to be ignored and attempts to correct formatting causes indentation specifications to be altered or eliminated. By bullets and numbering enabling, I mean that "include this paragraph" and/or "start numbering" is checked. I am using Open Office 4.2 in the current release of Ubuntu 14.04, presumably up to date, on an Pavilion laptop with AMD A8 processor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/1506696/+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 1093401] Re: [Upstream] 3 column address label mailmerge alignment not calculated correctly
** Changed in: libreoffice (Debian) 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/1093401 Title: [Upstream] 3 column address label mailmerge alignment not calculated correctly Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Incomplete Status in libreoffice package in Debian: Incomplete Bug description: When a 3 column label sheet is chosen for printing addresses with mailmerge, columns 2 and 3 are aligned further and further to the left. On Avery 5160, the rightmost column (3) is aligned so far to the left that it does not print fully on the label. This has been reported as Debian Bug #678813 and LibreOffice #58700. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Sun Dec 23 21:59:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-04-30 (238 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1093401/+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 1197870] Re: debian-changelog-mode support for non-coreutils systems
** Bug watch added: Debian Bug tracker #803767 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803767 ** Also affects: emacs-goodies-el via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803767 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs-goodies-el in Ubuntu. https://bugs.launchpad.net/bugs/1197870 Title: debian-changelog-mode support for non-coreutils systems Status in emacs-goodies: Unknown Status in emacs-goodies-el package in Ubuntu: Confirmed Bug description: The current debian-changelog-mode shells out to coreutils' date. To increase portability (some developers work on packages from other architectures), it would be nice to see this clean up get integrated: https://github.com/pcarrier/debian-changelog-mode/commit/fcf691df I get this should be reported upstream, but I won't pursue this further. Feel free to report/champion if this is of any interest to you. To manage notifications about this bug go to: https://bugs.launchpad.net/emacs-goodies-el/+bug/1197870/+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 1512576] [NEW] MTU is reset to 1280 often
Public bug reported: My interfaces on some state changes seems to reset the MTU to 1280 after connecting to Wifi, new interface, or around every 10 minutes on VPN. Seems to be an upstream bug with network-manager that wasn't fixed before release of 15.10 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a92d8b0c678e17d1cc175c3aad50afb1443785d2 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=c44069c10a4a9c696910baf0dbbefc41528f6dbe http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e0fa48f224abcb73a1a129f10050f7cd942ee629 All seem to be related. This is a major bug. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 2 22:15:13 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-31 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default dev vpn0 proto static scope link metric 50 default via 192.168.1.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev vpn0 scope link metric 1000 172.26.96.0/20 dev vpn0 proto kernel scope link src 172.26.108.224 metric 50 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.246 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-11-02T00:33:31.364599 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1512576 Title: MTU is reset to 1280 often Status in network-manager package in Ubuntu: New Bug description: My interfaces on some state changes seems to reset the MTU to 1280 after connecting to Wifi, new interface, or around every 10 minutes on VPN. Seems to be an upstream bug with network-manager that wasn't fixed before release of 15.10 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a92d8b0c678e17d1cc175c3aad50afb1443785d2 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=c44069c10a4a9c696910baf0dbbefc41528f6dbe http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e0fa48f224abcb73a1a129f10050f7cd942ee629 All seem to be related. This is a major bug. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 2 22:15:13 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-31 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default dev vpn0 proto static scope link metric 50 default via 192.168.1.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev vpn0 scope link metric 1000 172.26.96.0/20 dev vpn0 proto kernel scope link src 172.26.108.224 metric 50 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.246 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-11-02T00:33:31.364599 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/+bug/1512576/+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 1512578] [NEW] I always have to login my system with resume mode.
Public bug reported: My laptop is Lenovo Ideapad Z475, each time it won't access to my ubuntu 15.10 in the normal mode when I start my computer. I've tried to install fglrx but after reboot it even couldn't login to unity desk through resume mode. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.19.1-0ubuntu4 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 Date: Tue Nov 3 12:58:02 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397b] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon HD 6470M [17aa:397b] InstallationDate: Installed on 2015-11-01 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO IdeaPad Z475 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=UUID=7c6e6cbe-79ae-4faf-af48-0d3dfae2c220 ro recovery nomodeset Renderer: Software SourcePackage: xorg UdevLog: Error: [Errno 2] 没有那个文件或目录: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 53CN19WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: Lenovo KL6B/KL6C Z475 dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: Advanced Micro Devices, Inc. dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr53CN19WW:bd12/05/2011:svnLENOVO:pnIdeaPadZ475:pvrLenovoKL6B/KL6CZ475:rvnLENOVO:rnLenovo:rvrLenovoKL6B/KL6CZ475:cvnAdvancedMicroDevices,Inc.:ct10:cvrChassisVersionUnknown: dmi.product.name: IdeaPad Z475 dmi.product.version: Lenovo KL6B/KL6C Z475 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Nov 3 12:40:19 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu wily -- 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/1512578 Title: I always have to login my system with resume mode. Status in xorg package in Ubuntu: New Bug description: My laptop is Lenovo Ideapad Z475, each time it won't access to my ubuntu 15.10 in the normal mode when I start my computer. I've tried to install fglrx but after reboot it even couldn't login to unity desk through resume mode. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.19.1-0ubuntu4 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 Date: Tue Nov 3 12:58:02 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:397b] Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon HD 6470M [17aa:397b] InstallationDate: Installed on 2015-11-01 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO IdeaPad Z475 ProcKernelCmdLine:
[Desktop-packages] [Bug 1511905] Re: rhythmbox freezes on start of song
Aaand now the issue just went away. apt and dpkg not showing any updates since this report was filed. I'm at a loss as to potential explanations. Machine was not under heavy load during the time the symptoms were investigated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1511905 Title: rhythmbox freezes on start of song Status in rhythmbox package in Ubuntu: Confirmed Bug description: About 1s after starting a new song, rhythmbox uses 100% CPU (single core) and the UI freezes. Music continues to play fine. Thaws our after about one minute and interactions with GUI work fine until a new file is selected or starts automatically. Keyboard audio keys don't do anything during the freeze. This behaviour started out of the blue. Only suspect package that updated before it started is libaudiofile1, but I backdated that and the problem still occurred. Tried an strace but the machine froze. ltrace showed nothing obvious (to a non-linux dev like me anyway). Playing files with Totem did not show this issue. Neither did SMPlayer Ubuntu 14.04 Rhythmbox 3.0.2 amd64 binaries Tested with MP3 files only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1511905/+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 1511626] Re: gvfsd-smb crashed with signal 5 in g_settings_set_property()
No such directory in /usr/local The output of that command is: '' -- 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/1511626 Title: gvfsd-smb crashed with signal 5 in g_settings_set_property() Status in gvfs package in Ubuntu: New Bug description: Happens every time I try to mount a samba share. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gvfs-backends 1.24.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 Date: Fri Oct 30 06:32:26 2015 ExecutablePath: /usr/lib/gvfs/gvfsd-smb InstallationDate: Installed on 2015-07-12 (110 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 Signal: 5 SourcePackage: gvfs StacktraceTop: g_settings_set_property (object=0x1695f50 [GSettings], prop_id=, value=, pspec=) at /build/buildd/glib2.0-2.44.1/./gio/gsettings.c:521 g_object_new_internal (nqueue=, value=, pspec=, object=) at /build/buildd/glib2.0-2.44.1/./gobject/gobject.c:1415 g_object_new_internal (class=0x7f1d6cc47c00 , class@entry=0x16a, params=0x0, params@entry=0x7ffea81b7370, n_params=1) at /build/buildd/glib2.0-2.44.1/./gobject/gobject.c:1808 g_object_new_valist (object_type=object_type@entry=23644640, first_property_name=first_property_name@entry=0x7f1d6d4efc4f "schema-id", var_args=var_args@entry=0x7ffea81b74c0) at /build/buildd/glib2.0-2.44.1/./gobject/gobject.c:2033 g_object_new (object_type=23644640, first_property_name=0x7f1d6d4efc4f "schema-id") at /build/buildd/glib2.0-2.44.1/./gobject/gobject.c:1617 ThreadStacktrace: $4 = 0x4 Title: gvfsd-smb crashed with signal 5 in g_settings_set_property() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1511626/+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 1511259] Re: Session child does not inherit all LC_* variables
This bug was fixed in the package lightdm - 1.17.1-0ubuntu1 --- lightdm (1.17.1-0ubuntu1) xenial; urgency=medium * New upstream release: - Add a backup-logs option that can be used to disable existing logging files having a .old suffix added to them. - Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION variables to the list of inherited locale variables. (LP: #1511259) - Implement XDMCP ForwardQuery. (LP: #1511545) - Fix small memory leak in XDMCP logging code. -- Robert Ancell Tue, 03 Nov 2015 16:28:54 +1300 ** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- 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/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Not all system locale variables are passed to sessions. [Test Case] 1. Edit /etc/locale.conf and set LC_PAPER to a particular value 2. Start LightDM 3. Log into a session Expected result: LC_PAPER is set to the value in /etc/locale.conf Observed result: LC_PAPER is not set. [Regression potential] Low. We just added to an existing list of LC_* variables that are passed through to sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+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 1511545] Re: Implement XDMCP ForwardQuery
This bug was fixed in the package lightdm - 1.17.1-0ubuntu1 --- lightdm (1.17.1-0ubuntu1) xenial; urgency=medium * New upstream release: - Add a backup-logs option that can be used to disable existing logging files having a .old suffix added to them. - Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION variables to the list of inherited locale variables. (LP: #1511259) - Implement XDMCP ForwardQuery. (LP: #1511545) - Fix small memory leak in XDMCP logging code. -- Robert Ancell Tue, 03 Nov 2015 16:28:54 +1300 ** Changed in: lightdm (Ubuntu) Status: Triaged => Fix Released -- 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/1511545 Title: Implement XDMCP ForwardQuery Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] LightDM ignores the XDMCP ForwardQuery request. [Test Case] 1. Set up XDMCP so queries are forwarded through a server 2. Connect to LightDM Observed result: Connection fails Expected result: Connection succeeds. [Regression Potential] Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511545/+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 1511259] Re: Session child does not inherit all LC_* variables
The attachment "LC.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Not all system locale variables are passed to sessions. [Test Case] 1. Edit /etc/locale.conf and set LC_PAPER to a particular value 2. Start LightDM 3. Log into a session Expected result: LC_PAPER is set to the value in /etc/locale.conf Observed result: LC_PAPER is not set. [Regression potential] Low. We just added to an existing list of LC_* variables that are passed through to sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- 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/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Vivid: In Progress Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+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 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- 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/1504049 Title: Chromium not working in guest session (need more AppArmor rules) Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: In Progress Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Unable to run Chromium from guest session. [Test Case] 1. Start Ubuntu 2. From greeter select guest session 3. Load Chromium Expected result: Chromium runs. Observed result: Chromium does not run. [Regression Potential] Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1504049/+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 1470587] Re: dm-tool manpage has a typo
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- 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/1470587 Title: dm-tool manpage has a typo Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Small typo in dm-tool man page. [Test Case] 1. View man page: $ man dm-tool Expected result: Says "switch" Observed result: Says "swith" [Regression potential] About as low as you can get... To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1470587/+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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm/1.16 Status: Fix Committed => Fix Released -- 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/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+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 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** Changed in: lightdm/1.16 Status: Fix Committed => Fix Released -- 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/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+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 1511259] Re: Session child does not inherit all LC_* variables
** Changed in: lightdm/1.16 Status: Fix Committed => Fix Released -- 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/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Not all system locale variables are passed to sessions. [Test Case] 1. Edit /etc/locale.conf and set LC_PAPER to a particular value 2. Start LightDM 3. Log into a session Expected result: LC_PAPER is set to the value in /etc/locale.conf Observed result: LC_PAPER is not set. [Regression potential] Low. We just added to an existing list of LC_* variables that are passed through to sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+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 1511545] Re: Implement XDMCP ForwardQuery
** Changed in: lightdm/1.16 Status: Fix Committed => Fix Released ** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- 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/1511545 Title: Implement XDMCP ForwardQuery Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Vivid: In Progress Bug description: [Impact] LightDM ignores the XDMCP ForwardQuery request. [Test Case] 1. Set up XDMCP so queries are forwarded through a server 2. Connect to LightDM Observed result: Connection fails Expected result: Connection succeeds. [Regression Potential] Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511545/+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 1511259] Re: Session child does not inherit all LC_* variables
** Changed in: lightdm Status: Fix Committed => Fix Released -- 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/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Not all system locale variables are passed to sessions. [Test Case] 1. Edit /etc/locale.conf and set LC_PAPER to a particular value 2. Start LightDM 3. Log into a session Expected result: LC_PAPER is set to the value in /etc/locale.conf Observed result: LC_PAPER is not set. [Regression potential] Low. We just added to an existing list of LC_* variables that are passed through to sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+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 1511545] Re: Implement XDMCP ForwardQuery
** Changed in: lightdm Status: Fix Committed => Fix Released -- 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/1511545 Title: Implement XDMCP ForwardQuery Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Vivid: In Progress Bug description: [Impact] LightDM ignores the XDMCP ForwardQuery request. [Test Case] 1. Set up XDMCP so queries are forwarded through a server 2. Connect to LightDM Observed result: Connection fails Expected result: Connection succeeds. [Regression Potential] Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511545/+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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Vivid: In Progress Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+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 1470587] Re: dm-tool manpage has a typo
** Changed in: lightdm (Ubuntu Vivid) Status: Fix Committed => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1470587 Title: dm-tool manpage has a typo Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Small typo in dm-tool man page. [Test Case] 1. View man page: $ man dm-tool Expected result: Says "switch" Observed result: Says "swith" [Regression potential] About as low as you can get... To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1470587/+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 1481561] Re: Connect to XDMCP clients on address requests come from if available
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1481561 Title: Connect to XDMCP clients on address requests come from if available Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. [Test Case] 1. Start LightDM with XDMCP enabled 2. Connect with a client that puts a number of addresses in the Request packet Expected result: LightDM prefers the address the Request came from over the other addresses. Observed result: LightDM always picks the first address. [Regression Potential] There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1481561/+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 1507033] Re: lightdm.conf boolean values false if have trailing whitespace
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+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 1511545] Re: Implement XDMCP ForwardQuery
** Description changed: - If LightDM receives and XDMCP ForwardQuery it currently ignores it. It - should send back a Willing to the address specified in the query - request. + [Impact] + LightDM ignores the XDMCP ForwardQuery request. + + [Test Case] + 1. Set up XDMCP so queries are forwarded through a server + 2. Connect to LightDM + + Observed result: + Connection fails + + Expected result: + Connection succeeds. + + [Regression Potential] + Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => In Progress ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: lightdm (Ubuntu) Status: New => Triaged -- 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/1511545 Title: Implement XDMCP ForwardQuery Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Triaged Status in lightdm source package in Vivid: In Progress Bug description: [Impact] LightDM ignores the XDMCP ForwardQuery request. [Test Case] 1. Set up XDMCP so queries are forwarded through a server 2. Connect to LightDM Observed result: Connection fails Expected result: Connection succeeds. [Regression Potential] Some risk of existing XDMCP queries being broken by the change. Checked with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511545/+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 1468057] Re: Emit a warning about "logind-load-seats=true" and "xdg-seat=seatXXXX" option for LightDM 1.12+
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1468057 Title: Emit a warning about "logind-load-seats=true" and "xdg-seat=seat" option for LightDM 1.12+ Status in Light Display Manager: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. [Regression potential] Low. The change just checks for presence of an option and generates a log message. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1468057/+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 1504049] Re: Chromium not working in guest session (need more AppArmor rules)
** Changed in: lightdm (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1504049 Title: Chromium not working in guest session (need more AppArmor rules) Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Fix Released Status in chromium-browser source package in Trusty: New Status in lightdm source package in Trusty: Triaged Status in chromium-browser source package in Vivid: New Status in lightdm source package in Vivid: In Progress Status in chromium-browser source package in Wily: Confirmed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] Unable to run Chromium from guest session. [Test Case] 1. Start Ubuntu 2. From greeter select guest session 3. Load Chromium Expected result: Chromium runs. Observed result: Chromium does not run. [Regression Potential] Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1504049/+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 1511259] Re: Session child does not inherit all LC_* variables
** Description changed: - In file session-child.c in function session_child_run() variable - `locale_var_names` contains explicit list of locale environment - variables to inherit. This list lacks of some LC_* variables: LC_PAPER, - LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION. - As a result, these variables are not inherited by child session. - Therefore, processes inside desktop session set these variables to the - value of LANG, instead of appropriate values configured in - /etc/locale.conf. + [Impact] + Not all system locale variables are passed to sessions. - $ more /etc/locale.conf - LANG=en_US.UTF-8 - LC_CTYPE=pl_PL.UTF-8 - LC_NUMERIC=pl_PL.UTF-8 - LC_TIME=pl_PL.UTF-8 - LC_COLLATE=pl_PL.UTF-8 - LC_MONETARY=pl_PL.UTF-8 - LC_MESSAGES=en_US.UTF-8 - LC_PAPER=pl_PL.UTF-8 - LC_NAME=pl_PL.UTF-8 - LC_ADDRESS=pl_PL.UTF-8 - LC_TELEPHONE=pl_PL.UTF-8 - LC_MEASUREMENT=pl_PL.UTF-8 - LC_IDENTIFICATION=pl_PL.UTF-8 - LC_ALL= + [Test Case] + 1. Edit /etc/locale.conf and set LC_PAPER to a particular value + 2. Start LightDM + 3. Log into a session - Inside desktop session: + Expected result: + LC_PAPER is set to the value in /etc/locale.conf - $ locale - LANG=en_US.utf8 - LC_CTYPE=pl_PL.UTF-8 - LC_NUMERIC=pl_PL.UTF-8 - LC_TIME=pl_PL.UTF-8 - LC_COLLATE=pl_PL.UTF-8 - LC_MONETARY=pl_PL.UTF-8 - LC_MESSAGES=en_US.UTF-8 - LC_PAPER="en_US.utf8" - LC_NAME="en_US.utf8" - LC_ADDRESS="en_US.utf8" - LC_TELEPHONE="en_US.utf8" - LC_MEASUREMENT="en_US.utf8" - LC_IDENTIFICATION="en_US.utf8" - LC_ALL= + Observed result: + LC_PAPER is not set. - Notice wrong values of LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, - LC_MEASUREMENT and LC_IDENTIFICATION (en_US.utf8 instead pl_PL.UTF-8). - - Fix: - - Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and - LC_IDENTIFICATION to the `locale_var_names` array in file session- - child.c. + [Regression potential] + Low. We just added to an existing list of LC_* variables that are passed through to sessions. ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Not all system locale variables are passed to sessions. [Test Case] 1. Edit /etc/locale.conf and set LC_PAPER to a particular value 2. Start LightDM 3. Log into a session Expected result: LC_PAPER is set to the value in /etc/locale.conf Observed result: LC_PAPER is not set. [Regression potential] Low. We just added to an existing list of LC_* variables that are passed through to sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm (Ubuntu Vivid) Status: Fix Committed => In Progress ** Changed in: lightdm (Ubuntu Vivid) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: In Progress Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+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 1470587] Re: dm-tool manpage has a typo
** Description changed: - Running Ubuntu 14.04.2 LTS on armhf with lightdm version 1.10.5-0ubuntu1 + [Impact] + Small typo in dm-tool man page. - The the dm-tool lock option has a typo that says "swith" instead of - "switch" in the manpage + [Test Case] + 1. View man page: + $ man dm-tool + + Expected result: + Says "switch" + + Observed result: + Says "swith" + + [Regression potential] + About as low as you can get... ** No longer affects: lightdm (Ubuntu Wily) ** No longer affects: lightdm (Ubuntu 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/1470587 Title: dm-tool manpage has a typo Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: [Impact] Small typo in dm-tool man page. [Test Case] 1. View man page: $ man dm-tool Expected result: Says "switch" Observed result: Says "swith" [Regression potential] About as low as you can get... To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1470587/+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 1511259] Re: Session child does not inherit all LC_* variables
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** Also affects: ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu (Ubuntu) Status: Fix Released => Fix Committed ** Package changed: ubuntu (Ubuntu) => lightdm (Ubuntu) ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => In Progress ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium -- 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/1511259 Title: Session child does not inherit all LC_* variables Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Vivid: In Progress Bug description: In file session-child.c in function session_child_run() variable `locale_var_names` contains explicit list of locale environment variables to inherit. This list lacks of some LC_* variables: LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION. As a result, these variables are not inherited by child session. Therefore, processes inside desktop session set these variables to the value of LANG, instead of appropriate values configured in /etc/locale.conf. $ more /etc/locale.conf LANG=en_US.UTF-8 LC_CTYPE=pl_PL.UTF-8 LC_NUMERIC=pl_PL.UTF-8 LC_TIME=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 LC_MONETARY=pl_PL.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=pl_PL.UTF-8 LC_NAME=pl_PL.UTF-8 LC_ADDRESS=pl_PL.UTF-8 LC_TELEPHONE=pl_PL.UTF-8 LC_MEASUREMENT=pl_PL.UTF-8 LC_IDENTIFICATION=pl_PL.UTF-8 LC_ALL= Inside desktop session: $ locale LANG=en_US.utf8 LC_CTYPE=pl_PL.UTF-8 LC_NUMERIC=pl_PL.UTF-8 LC_TIME=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 LC_MONETARY=pl_PL.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= Notice wrong values of LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION (en_US.utf8 instead pl_PL.UTF-8). Fix: Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION to the `locale_var_names` array in file session- child.c. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1511259/+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 1507033] Re: lightdm.conf is sensitive to trailing whitespace
** Also affects: ubuntu Importance: Undecided Status: New ** Also affects: Ubuntu Vivid Importance: Undecided Status: New ** Package changed: ubuntu => lightdm (Ubuntu) ** Changed in: lightdm (Ubuntu) Status: New => Fix Released ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium ** Summary changed: - lightdm.conf is sensitive to trailing whitespace + lightdm.conf boolean values false if have trailing whitespace ** Description changed: - It appears that lightdm.conf is sensitive to trailing spaces. I get - different behavior with + [Impact] + Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. - greeter-hide-users=true + [Test Case] + 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) + 2. Run LightDM - and + Expected result: + The configured value is interpreted as true. - greeter-hide-users=true_ + Observed result: + The configured value is interpreted as false. - where the _ in the second example represents a trailing space. Without - the space, the greeter hides the list of users as I expected. With the - space, the greeter displays the list of users as if the greeter-hide- - users parameter is not set to true. + [Regression potential] + Low. We just strip trailing whitespace when checking for the value "true". -- 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/1507033 Title: lightdm.conf boolean values false if have trailing whitespace Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Triaged Bug description: [Impact] Adding trailing whitespace to a boolean true value in LightDM configuration has it read as false. [Test Case] 1. Set a boolean configuration value in lightdm.conf to true_ (_ is a space character) 2. Run LightDM Expected result: The configured value is interpreted as true. Observed result: The configured value is interpreted as false. [Regression potential] Low. We just strip trailing whitespace when checking for the value "true". To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1507033/+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 1481561] Re: Connect to XDMCP clients on address requests come from if available
** Description changed: - Currently LightDM connects to an XDMCP enabled X server using the first - suitable address in the XDMCP Request packet. However, some clients may - put a number of addresses in this message and potentially they are not - all routable. If the address the request message came from is in the - list we should use that first as that is more likely to be a routable - address. This also matches the behaviour of GDM which ignores the - contents of the Request packet anyway. + [Impact] + Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. + + [Test Case] + 1. Start LightDM with XDMCP enabled + 2. Connect with a client that puts a number of addresses in the Request packet + + Expected result: + LightDM prefers the address the Request came from over the other addresses. + + Observed result: + LightDM always picks the first address. + + [Regression Potential] + There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). ** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium -- 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/1481561 Title: Connect to XDMCP clients on address requests come from if available Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.2 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Triaged Bug description: [Impact] Currently LightDM connects to an XDMCP enabled X server using the first suitable address in the XDMCP Request packet. However, some clients may put a number of addresses in this message and potentially they are not all routable. If the address the request message came from is in the list we should use that first as that is more likely to be a routable address. This also matches the behaviour of GDM which ignores the contents of the Request packet anyway. [Test Case] 1. Start LightDM with XDMCP enabled 2. Connect with a client that puts a number of addresses in the Request packet Expected result: LightDM prefers the address the Request came from over the other addresses. Observed result: LightDM always picks the first address. [Regression Potential] There is a possibility of a behaviour change in existing clients that had two valid addresses, though the particular address shouldn't matter (unless complex firewalling / routing rules are being used). There is a risk that XDMCP behaviour could have been broken by the change (tested with regression tests). To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1481561/+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 1468057] Re: Emit a warning about "logind-load-seats=true" and "xdg-seat=seatXXXX" option for LightDM 1.12+
** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Description changed: - LightDM 1.12 introduced a new logind-based mechanism for loading seats. - Such a feature was later backported to 1.10.3 (so it can be used in - Ubuntu 14.04 LTS), but it was made optional: + [Impact] - [LightDM] - logind-load-seats=true + [Test Case] + 1. Add login-load-seats=true into lightdm.conf + 2. Run LightDM + 3. Check /var/log/lightdm/lightdm.log - Now that we're halfway from a new Ubuntu LTS release, I think it would - be useful if next LightDM release could emit a warning about "logind- - load-seats=true" deprecation if it's set in lightdm.conf. Something like - this: + Expected result: + A warning should be there that this option is no longer required. - WARNING: Option "logind-load-seats=true" was specific for 1.10 series. - You can safely remove it now. + Observed result: + No warning is shown. ** Description changed: [Impact] + Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. ** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released ** Description changed: [Impact] Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. + + [Regression potential] + Low. The change just checks for presence of an option and generates a log message. -- 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/1468057 Title: Emit a warning about "logind-load-seats=true" and "xdg-seat=seat" option for LightDM 1.12+ Status in Light Display Manager: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Triaged Bug description: [Impact] Old configuration no longer has an effect but user is not given information so they can remove it. [Test Case] 1. Add login-load-seats=true into lightdm.conf 2. Run LightDM 3. Check /var/log/lightdm/lightdm.log Expected result: A warning should be there that this option is no longer required. Observed result: No warning is shown. [Regression potential] Low. The change just checks for presence of an option and generates a log message. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1468057/+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 1511259] [NEW] Session child does not inherit all LC_* variables
You have been subscribed to a public bug: In file session-child.c in function session_child_run() variable `locale_var_names` contains explicit list of locale environment variables to inherit. This list lacks of some LC_* variables: LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION. As a result, these variables are not inherited by child session. Therefore, processes inside desktop session set these variables to the value of LANG, instead of appropriate values configured in /etc/locale.conf. $ more /etc/locale.conf LANG=en_US.UTF-8 LC_CTYPE=pl_PL.UTF-8 LC_NUMERIC=pl_PL.UTF-8 LC_TIME=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 LC_MONETARY=pl_PL.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=pl_PL.UTF-8 LC_NAME=pl_PL.UTF-8 LC_ADDRESS=pl_PL.UTF-8 LC_TELEPHONE=pl_PL.UTF-8 LC_MEASUREMENT=pl_PL.UTF-8 LC_IDENTIFICATION=pl_PL.UTF-8 LC_ALL= Inside desktop session: $ locale LANG=en_US.utf8 LC_CTYPE=pl_PL.UTF-8 LC_NUMERIC=pl_PL.UTF-8 LC_TIME=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 LC_MONETARY=pl_PL.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= Notice wrong values of LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION (en_US.utf8 instead pl_PL.UTF-8). Fix: Add LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEASUREMENT and LC_IDENTIFICATION to the `locale_var_names` array in file session- child.c. ** Affects: lightdm Importance: Medium Status: Fix Committed ** Affects: lightdm/1.10 Importance: Medium Status: Fix Committed ** Affects: lightdm/1.14 Importance: Medium Status: Fix Released ** Affects: lightdm/1.16 Importance: Medium Status: Fix Committed ** Affects: lightdm/1.2 Importance: Medium Status: Won't Fix ** Affects: lightdm (Ubuntu) Importance: Medium Status: Fix Committed -- Session child does not inherit all LC_* variables https://bugs.launchpad.net/bugs/1511259 You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm 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 1478087] Re: Add libaudit support
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- 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/1478087 Title: Add libaudit support Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in audit package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in openssh source package in Trusty: Triaged Status in shadow source package in Trusty: Triaged Status in lightdm source package in Vivid: Triaged Status in openssh source package in Vivid: Triaged Status in shadow source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Status in openssh source package in Wily: Fix Released Status in shadow source package in Wily: Fix Released Bug description: -- Problem Description -- We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login info. root@lakelp1:~# /etc/init.d/auditd status * auditd is running. root@lakelp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1 root@lakelp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1 type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1 type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1 type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1 type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1 root@lakelp1:~# aureport -l Login Report # date time auid host term exe success event This looks like a bug in aureport or libaudit. In addition to giving admins falsely empty record selections, this would prevent successful completion of a Common Criteria certification. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1478087/+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 1507033] [NEW] lightdm.conf is sensitive to trailing whitespace
You have been subscribed to a public bug: It appears that lightdm.conf is sensitive to trailing spaces. I get different behavior with greeter-hide-users=true and greeter-hide-users=true_ where the _ in the second example represents a trailing space. Without the space, the greeter hides the list of users as I expected. With the space, the greeter displays the list of users as if the greeter-hide- users parameter is not set to true. ** Affects: lightdm Importance: Medium Status: Fix Released ** Affects: lightdm/1.10 Importance: Medium Status: Fix Committed ** Affects: lightdm/1.14 Importance: Medium Status: Fix Committed ** Affects: lightdm/1.16 Importance: Medium Status: Fix Committed ** Affects: lightdm/1.2 Importance: Medium Status: Fix Committed ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New -- lightdm.conf is sensitive to trailing whitespace https://bugs.launchpad.net/bugs/1507033 You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm 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 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
** Changed in: lightdm/1.14 Status: Fix Committed => Fix Released -- 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/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Committed Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+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 1512527] Re: fglrx-core (not installed): fglrx-core kernel module failed to build [firegl_public.c:194:22: fatal error: asm/i387.h: Arquivo ou diretório não encontrado]
** Summary changed: - fglrx-core (not installed): fglrx-core kernel module failed to build [I can't install HD Radeon 8850m drivers] + fglrx-core (not installed): fglrx-core kernel module failed to build [firegl_public.c:194:22: fatal error: asm/i387.h: Arquivo ou diretório não encontrado] -- 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/1512527 Title: fglrx-core (not installed): fglrx-core kernel module failed to build [firegl_public.c:194:22: fatal error: asm/i387.h: Arquivo ou diretório não encontrado] Status in fglrx-installer package in Ubuntu: New Bug description: I can't install AMD HD Radeon 8850M drivers. No open source or proprietary are working. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: fglrx-core 2:15.201-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 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 DKMSKernelVersion: 4.2.0-16-generic Date: Mon Nov 2 20:54:16 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201: added virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05eb] Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] [1002:6823] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05eb] InstallationDate: Installed on 2015-10-22 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5537 PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=3ba6a9e1-3426-4934-8b31-d21b50ed0a54 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: fglrx-installer Title: fglrx-core (not installed): fglrx-core kernel module failed to build UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RXM8D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn0RXM8D:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5537 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Nov 2 20:56:34 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1512527/+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 1512417] Re: fglrx gcc5 patch doesn't fix crash on 4.3 kernel
*** This bug is a duplicate of bug 1502978 *** https://bugs.launchpad.net/bugs/1502978 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1502978, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1502978 fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build against kernel 4.3 [firegl_public.c:639:9: error: void value not ignored as it ought to be] -- 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/1512417 Title: fglrx gcc5 patch doesn't fix crash on 4.3 kernel Status in fglrx-installer-updates package in Ubuntu: New Bug description: fglrx-installer-updates (2:15.201-0ubuntu2~15.10.2) wily-proposed does not fix crash on startup on the 4.3 stable kernel. Installed from ubuntu mainline ppa. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: fglrx-updates-core 2:15.201-0ubuntu2~15.10.2 Uname: Linux 4.2.5-040205-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 BootLog: fsck from util-linux 2.26.2 /dev/sda3: recovering journal /dev/sda3: clean, 387094/1204224 files, 1861663/4811520 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.3.0-040300rc7-generic Date: Sun Nov 1 18:00:15 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.201, 4.0.5-040005-generic, x86_64: installed fglrx-updates-core, 15.201, 4.2.5-040205-generic, x86_64: installed virtualbox, 5.0.4, 4.0.5-040005-generic, x86_64: installed virtualbox, 5.0.4, 4.2.5-040205-generic, x86_64: installed DuplicateSignature: dkms:fglrx-updates-core:2:15.201-0ubuntu2~15.10.2:/var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0b00] InstallationDate: Installed on 2015-10-23 (9 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageVersion: 2:15.201-0ubuntu2~15.10.2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.5-040205-generic root=UUID=e46d88f9-1a02-4f78-9ff3-fa4aeaf7e1c1 ro noprompt quiet splash RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: fglrx-installer-updates Title: fglrx-updates-core 2:15.201-0ubuntu2~15.10.2: fglrx-updates-core kernel module failed to build UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H97 Pro4 dmi.board.vendor: ASRock 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.:bvrP1.80:bd05/13/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Pro4:rvr: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 N/A version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Nov 2 11:51:58 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.
[Desktop-packages] [Bug 1512156] Re: bypassing password request by pressing 'cancel' 4 times
Can you get a screenshot of the dialog? You shouldn't need a password to change the proxy settings. ** Changed in: unity-control-center (Ubuntu) Status: New => Incomplete -- 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/1512156 Title: bypassing password request by pressing 'cancel' 4 times Status in unity-control-center package in Ubuntu: Incomplete Bug description: I have setup a 'maunal' proxy under network > network proxy. To set it up I have entered by password. After a while (also after restarting the control center) I change the form form 'manual' to 'none'. A window pops up which requests my password to perform the changes. When I press 'cancel' four times, the changes are applied, without the password! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17 Uname: Linux 3.16.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 1 22:08:52 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-03-05 (241 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4 gnome-control-center 1:3.6.3-0ubuntu56.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1512156/+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 371897]
(In reply to Sebastian Lackner from comment #428) > Closing this bug was probably a bit rushed, to quote Andrews comment on > wine-devel: > > """After those five, there are three more patches to implement missing > critical interfaces (volume, session, and marshalling).""" > > I would assume the current state is not fully functional enough to actually > use it. Should wait to see if those additional patches are added. If they're not, then create new bugs for implementing those interfaces. This thread is already insanely long, and the primary issue (proper PulseAudio support) is now fixed upstream. -- 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/371897 Title: Occasional sound drops in Wine via PulseAudio Status in Wine: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in wine package in Ubuntu: Fix Released Bug description: Binary package hint: wine I'm running the Spotify Windows application on two laptops under Wine with both internal and external USB sound card. With both cards you get the occasional pop and click in the sound suggesting some data loss somewhere. I've selected the alsa drivers in winecfg and the whole thing is running via the alsa compatibility layer in pulseaudio. Jaunty 9.04 UNR and standard Ubuntu desktop. wine: Installed: 1.0.1-0ubuntu6 Candidate: 1.0.1-0ubuntu6 Version table: *** 1.0.1-0ubuntu6 0 500 http://gb.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status pulseaudio: Installed: 1:0.9.14-0ubuntu20 Candidate: 1:0.9.14-0ubuntu20 Version table: *** 1:0.9.14-0ubuntu20 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+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 1371274] Re: Unable to use the widevine plugin with Chromium
@Ekimia that's awesome news. Do you have a plan to distribute the package for the RaspberryPi 2 (armhf)? Once that's supported, it's the last piece in being able to setup a home theatre with OSMC/Kodi/XBMC that has native Netflix support :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1371274 Title: Unable to use the widevine plugin with Chromium Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium is unable to use the widevine component from google chrome : libwidevinecdmadapter.so and libwidevinecdm.so How to reproduce : - copy the 2 files the chrome archive in /usr/lib/chromium-browser - check chrome://components/ - Widevine does not appear Solution : With the help from several people (hogliux for patch and saiarcot895 for PPA) , a PPA is available with this feature : - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev - You need the binary widevine plugin plugin (2 files) : https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz To be copied in /usr/lib/chromium - Launch netflix.com and see if it works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042 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 Date: Thu Sep 18 21:11:17 2014 InstallationDate: Installed on 2013-10-02 (350 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'system-image-cli' UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1371274/+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 1512546] Re: System Crashes while using Firefox 41.0.2
** Description changed: xorg crashes - screen black then to the login prompt. Seems to always occur while firefox is running. Can't reproduce without firefox running. Flash is not always running during crash. Other programs particularly NetBeans running simultaneously seem to increase likelyhood of crash. - This typically occurs when a lot of changes have been made and a new - action is taken in firefox. + This typically occurs when I spend a lot of time in netbeans, lots of + changes, saves, etc then move back to firefox and navigate anywhere. + However occasionally I will be working on the netbeans side with firefox + open in the background and the crash will occur. While actively working + the crash occurs about once an hour. Left alone the computer appears + stable. I'm running a dual monitor, 1st monitor is a built in screen on + a dell inspiron. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic i686 .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,snap,place,regex,mousepoll,wall,imgpng,session,move,unitymtgrabhandles,vpswitch,resize,compiztoolbox,gnomecompat,grid,animation,workarounds,expo,fade,scale,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 2 20:04:55 2015 DistUpgraded: 2014-10-25 15:03:53,192 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:04d8] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:04d8] InstallationDate: Installed on 2011-08-08 (1547 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: Dell Inc. Dell System Inspiron N7110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic root=UUID=9f718709-f805-4752-89fd-8ca3e8c9acf3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-10-25 (373 days ago) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YH79Y 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.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn0YH79Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N7110 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 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.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Nov 2 19:59:25 2015 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 535 - vendor SAM + product id 535 + vendor SAM xserver.version: 2:1.15.1-0ubuntu2.7 -- 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/1512546 Title: System Crashes while using Firefox 41.0.2 Status in xorg package in Ubuntu: New Bug description: xorg crashes - screen black then to the login prompt. Seems to always occur while firefox is running. Can't reproduce without firefox running. Flash is not always running during crash. Other programs particularly NetBeans running simultaneously seem to increase likelyhood of crash. This typically occurs when I spend a lot of time in netbeans, lots of changes, saves, etc then move back to firefox and navigate anywhere. However occasionally I will be working on the netbeans side with firefox open in the background and the crash will occur. While actively working the crash occurs about once an hour. Left alone the compute
[Desktop-packages] [Bug 1512546] [NEW] System Crashes while using Firefox 41.0.2
Public bug reported: xorg crashes - screen black then to the login prompt. Seems to always occur while firefox is running. Can't reproduce without firefox running. Flash is not always running during crash. Other programs particularly NetBeans running simultaneously seem to increase likelyhood of crash. This typically occurs when I spend a lot of time in netbeans, lots of changes, saves, etc then move back to firefox and navigate anywhere. However occasionally I will be working on the netbeans side with firefox open in the background and the crash will occur. While actively working the crash occurs about once an hour. Left alone the computer appears stable. I'm running a dual monitor, 1st monitor is a built in screen on a dell inspiron. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,snap,place,regex,mousepoll,wall,imgpng,session,move,unitymtgrabhandles,vpswitch,resize,compiztoolbox,gnomecompat,grid,animation,workarounds,expo,fade,scale,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 2 20:04:55 2015 DistUpgraded: 2014-10-25 15:03:53,192 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04d8] InstallationDate: Installed on 2011-08-08 (1547 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: Dell Inc. Dell System Inspiron N7110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic root=UUID=9f718709-f805-4752-89fd-8ca3e8c9acf3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-10-25 (373 days ago) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YH79Y 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.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemInspironN7110:pvr:rvnDellInc.:rn0YH79Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron N7110 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 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.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Nov 2 19:59:25 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 535 vendor SAM xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty 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/1512546 Title: System Crashes while using Firefox 41.0.2 Status in xorg package in Ubuntu: New Bug description: xorg crashes - screen black then to the login prompt. Seems to always occur while firefox is running. Can't reproduce without firefox running. Flash is not always running during crash. Other programs particularly NetBeans running simultaneously seem to increase likelyhood of crash. This typically occurs when I spend a lot of time in netbeans, lots of changes, saves, etc then move back to firefox and navigate anywhere. However occasionally I will be working on the netbeans side with firefox open in the background and the crash will occur. While actively working the crash occurs about once an hour. Left alone the computer appears stable. I'm running a dual monitor, 1st monitor is a built in screen on a dell inspiron. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 CompizPlugins: [core,bailer,dete
[Desktop-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10
Thought this was duplicate of https://bugs.launchpad.net/ubuntu/+source /xserver-xorg-video-intel/+bug/1510970, but the stack trace is slightly different (See Johan Tol's stack trace above which is exactly what is seen in 1510970) -- 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/1510998 Title: Xorg crashes with segfault on 15.10 Status in xorg package in Ubuntu: Confirmed Bug description: I updated my system from 15.04 to 15.10 yesterday. Since then the X server has already crashed 5 times, which renders the system close to unusable for me. The corresponding messages in Xorg.0.log.old are: [ 12125.023] (EE) [ 12125.023] (EE) Backtrace: [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e] [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999] [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) [0x7f7c10eb02f0] [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x24edc) [0x7f7c0d276edc] [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x26157) [0x7f7c0d278157] [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8] [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec] [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x59103) [0x7f7c0d2ab103] [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa] [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73] [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3] [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f] [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b] [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f7c10e9ba40] [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9] [ 12125.023] (EE) [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0 [ 12125.023] (EE) Fatal server error: [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting I have attached the syslog file. The relevant messages for the three crashes from today can be found at: Oct 28 15:56:36 Oct 28 12:06:58 Oct 28 09:08:51 Unfortunately I have no clue how to reproduce the segfault. The last crash happened while I was reading some document and I did not push any button, moved the mouse or anything... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Oct 28 16:30:43 2015 DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: kubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:091c] InstallationDate: Installed on 2015-01-20 (281 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Acer Aspire VN7-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571G dmi.board
[Desktop-packages] [Bug 1512529] [NEW] Chromium 43 fails to use hardware acceleration
Public bug reported: Please reopen https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1463598 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1512529 Title: Chromium 43 fails to use hardware acceleration Status in chromium-browser package in Ubuntu: New Bug description: Please reopen https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1463598 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1512529/+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 1463598] Re: Chromium 43 fails to use hardware acceleration
I do have "Use hardware acceleration when available", still chrome://gpu shows a lot of disabled/software-only stuff. THIS IS NOT F***ING FIXED. Watching videos consumes a lot of CPU, and so does even just opening a page with a few small animated gifs. This is f***ing ridiculous. Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Rasterization: Software only. Hardware acceleration disabled Video Decode: Software only, hardware acceleration unavailable Video Encode: Hardware accelerated WebGL: Hardware accelerated Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_post_sub_buffers_for_onscreen_surfaces init_gl_position_in_vertex_shader init_vertex_attributes remove_pow_with_constant_exponent scalarize_vec_and_mat_constructor_args use_current_program_after_successful_link use_virtualized_gl_contexts Problems Detected Accelerated 2d canvas is unstable in Linux at the moment Disabled Features: accelerated_2d_canvas Accelerated video decode is unavailable on Linux: 137247 Disabled Features: accelerated_video_decode Always call glUseProgram after a successful link to avoid a driver bug: 349137 Applied Workarounds: use_current_program_after_successful_link Program link fails in NVIDIA Linux if gl_Position is not set: 286468 Applied Workarounds: init_gl_position_in_vertex_shader Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Mesa drivers in Linux handle varyings without static use incorrectly: 333885 Applied Workarounds: count_all_in_varyings_packing Linux NVIDIA drivers don't have the correct defaults for vertex attributes: 351528 Applied Workarounds: init_vertex_attributes Disable partial swaps on linux drivers: 339493 Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args MakeCurrent is slow on Linux Applied Workarounds: use_virtualized_gl_contexts NVIDIA 331 series drivers shader compiler may crash when attempting to optimize pow(): 477306 Applied Workarounds: remove_pow_with_constant_exponent Accelerated rasterization has been disabled, either via about:flags or command line. Disabled Features: rasterization -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1463598 Title: Chromium 43 fails to use hardware acceleration Status in chromium-browser package in Ubuntu: Fix Released Bug description: After installing package chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 hardware acceleration becomes disabled. I had no problem with previous chromium version. Console output: $ chromium-browser [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process. [3150:3150:0609/190556:ERROR:url_pattern_set.cc(240)] Invalid url pattern: chrome://print/* [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process. [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process. chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_chromium_framebuffer_multisample disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all - - - Actually GPU access is *not* disabled from settings. Workarounds like "--disable-gpu-sandbox" or "LIBGL_DRI3_DISABLE=1" didn't helped at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1463598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https
[Desktop-packages] [Bug 1512527] [NEW] fglrx-core (not installed): fglrx-core kernel module failed to build [I can't install HD Radeon 8850m drivers]
Public bug reported: I can't install AMD HD Radeon 8850M drivers. No open source or proprietary are working. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: fglrx-core 2:15.201-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 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 DKMSKernelVersion: 4.2.0-16-generic Date: Mon Nov 2 20:54:16 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201: added virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05eb] Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] [1002:6823] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05eb] InstallationDate: Installed on 2015-10-22 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Inspiron 5537 PackageVersion: (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=3ba6a9e1-3426-4934-8b31-d21b50ed0a54 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: fglrx-installer Title: fglrx-core (not installed): fglrx-core kernel module failed to build UdevLog: Error: [Errno 2] Arquivo ou diretório não encontrado: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RXM8D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn0RXM8D:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5537 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Nov 2 20:56:34 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 ubuntu wily -- 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/1512527 Title: fglrx-core (not installed): fglrx-core kernel module failed to build [I can't install HD Radeon 8850m drivers] Status in fglrx-installer package in Ubuntu: New Bug description: I can't install AMD HD Radeon 8850M drivers. No open source or proprietary are working. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: fglrx-core 2:15.201-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 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 DKMSKernelVersion: 4.2.0-16-generic Date: Mon Nov 2 20:54:16 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201: added virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05eb] Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] [1002:6823] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05eb] InstallationDate: Installed on 2015-10-22 (11 days ago) InstallationMedia
[Desktop-packages] [Bug 1512524] [NEW] /usr/lib/gvfs/gvfsd-afp-browse:5:read_dsi_header_cb:g_simple_async_result_complete:read_all_cb:async_ready_callback_wrapper:g_task_return_now
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with version 1.24.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/62e1c3b8a03258a3648c247e41ca31a52d6b863b contains more details. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: kylin-15.04 trusty vivid wily -- 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/1512524 Title: /usr/lib/gvfs/gvfsd-afp- browse:5:read_dsi_header_cb:g_simple_async_result_complete:read_all_cb:async_ready_callback_wrapper:g_task_return_now Status in gvfs package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with version 1.24.2-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/62e1c3b8a03258a3648c247e41ca31a52d6b863b contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1512524/+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 935296] Re: java-atk-wrapper prevents java applications from starting
Just gonna link this ticket in here @samuel: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1510009 Seems that the ATK wrapper is causing issues for Java 8 in Wily. Interestingly enough Java 7 is still disabled, referencing this bug: # Doesn't work, see LP: #935296 #assistive_technologies=org.GNOME.Accessibility.AtkWrapper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/935296 Title: java-atk-wrapper prevents java applications from starting Status in java-atk-wrapper package in Ubuntu: Fix Released Status in openjdk-6 package in Ubuntu: Fix Released Status in openjdk-7 package in Ubuntu: Fix Released Status in java-atk-wrapper source package in Precise: Confirmed Status in openjdk-6 source package in Precise: Triaged Status in openjdk-7 source package in Precise: Triaged Status in java-atk-wrapper package in Debian: Fix Released Bug description: default java at command line is still java6. invoke java from command line, and minecraft fails to start, usually with no message, but there is some variety. Most usual: charles@basquette:~/Desktop$ java -jar ./minecraft.jar Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-oSohfHsLYR: Connection refused charles@basquette:~/Desktop$ another case: charles@basquette:~/Desktop$ java -jar ./minecraft.jar Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-oSohfHsLYR: Connection refused [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. java: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Aborted (core dumped) charles@basquette:~/Desktop$ another version, as suggested by: http://ubuntuforums.org/showthread.php?p=11696963 is to invoke as root, yielding: root@basquette:/home/charles/Desktop# java -jar ./minecraft.jar Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ** WARNING **: Unable to create Ubuntu Menu Proxy: The connection is closed ** WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-oSohfHsLYR: Connection refused java.io.FileNotFoundException: /root/.minecraft/lastlogin (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:137) at net.minecraft.LoginForm.readUsername(LoginForm.java:131) at net.minecraft.LoginForm.(LoginForm.java:76) at net.minecraft.LauncherFrame.(LauncherFrame.java:30) at net.minecraft.LauncherFrame.main(LauncherFrame.java:158) at net.minecraft.MinecraftLauncher.main(MinecraftLauncher.java:13) ^Croot@basquette:/home/charles/Desktop# exit minecraft is stock .jar unchanged for several weeks/months ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: openjdk-6-jre 6b24-1.11.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sat Feb 18 09:39:32 2012 InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openjdk-6 UpgradeStatus: Upgraded to precise on 2012-01-15 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/935296/+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 1512521] Re: gvfs-trash fails on file in a symbolic linked folder in a different file system
I actually noticed this on thunar but I drilled it down to gvfs-trash.
--
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/1512521
Title:
gvfs-trash fails on file in a symbolic linked folder in a different
file system
Status in gvfs package in Ubuntu:
New
Bug description:
I have Documents in a LUKS container mounted and symlinked on my home folder.
|-- Documents -> secure/documents
Have other folders like Desktop in a ecryptfs folder mounted and symlinked on
my home folder.
|-- Desktop -> Private/Desktop
So when I delete a file on Desktop or Documents it fails. It seems like it's
saving the file in .local/share/trash instead of inside the containers. I was
using fedora 22 and it was working fine. Now moved to ubuntu 15.10 and doesn't
seem to work.
strace of trying to delete the file:
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/gvfs/modules",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
lstat("/home/zed/Documents/secure-trash.txt", {st_mode=S_IFREG|0664,
st_size=0, ...}) = 0
stat("/home/zed", {st_mode=S_IFDIR|0700, st_size=894, ...}) = 0
lstat("/home/zed/Documents", {st_mode=S_IFLNK|0777, st_size=16, ...}) = 0
access("/home", F_OK) = 0
stat("/home", {st_mode=S_IFDIR|0755, st_size=50, ...}) = 0
access("/home/zed", F_OK) = 0
stat("/home/zed", {st_mode=S_IFDIR|0700, st_size=894, ...}) = 0
access("/home/zed/.local", F_OK) = 0
stat("/home/zed/.local", {st_mode=S_IFDIR|0700, st_size=10, ...}) = 0
access("/home/zed/.local/share", F_OK) = 0
stat("/home/zed/.local/share", {st_mode=S_IFDIR|0700, st_size=224, ...}) = 0
access("/home/zed/.local/share/Trash", F_OK) = 0
stat("/home/zed/.local/share/Trash", {st_mode=S_IFDIR|0700, st_size=34, ...})
= 0
mkdir("/home/zed/.local/share/Trash/info", 0700) = -1 EEXIST (File exists)
mkdir("/home/zed/.local/share/Trash/files", 0700) = -1 EEXIST (File exists)
open("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo",
O_RDONLY|O_CREAT|O_EXCL, 0666) = 3
close(3)= 0
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=3687, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=3687, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7feb9f31b000
read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10\0\0\0\0"...,
4096) = 3687
lseek(3, -2347, SEEK_CUR) = 1340
read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10\0\0\0\0"...,
4096) = 2347
close(3)= 0
munmap(0x7feb9f31b000, 4096)= 0
open("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo.DITD7X",
O_RDWR|O_CREAT|O_EXCL, 0666) = 3
fallocate(3, 0, 0, 94) = 0
write(3, "[Trash Info]\nPath=/home/bpmarinh"..., 94) = 94
fstatfs(3, {f_type=0x9123683e, f_bsize=4096, f_blocks=119953152,
f_bfree=76651779, f_bavail=76103891, f_files=0, f_ffree=0, f_fsid={-810601384,
-1547478495}, f_namelen=255, f_frsize=4096}) = 0
close(3)= 0
rename("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo.DITD7X",
"/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo") = 0
rename("/home/zed/Documents/secure-trash.txt",
"/home/zed/.local/share/Trash/files/secure-trash.txt") = -1 EXDEV (Invalid
cross-device link)
unlink("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo") = 0
open("/dev/tty", O_RDWR|O_NOCTTY|O_NONBLOCK) = 3
writev(3, [{"*** Error in `", 14}, {"gvfs-trash", 10}, {"': ", 3}, {"double
free or corruption (fastt"..., 35}, {": 0x", 4}, {"01222aa0", 16}, {"
***\n", 5}], 7*** Error in `gvfs-trash': double free or corruption (fasttop):
0x01222aa0 ***
) = 87
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7feb9f31b000
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(5432, 5432, SIGABRT) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=5432, si_uid=1000} ---
+++ killed by SIGABRT (core dumped) +++
Aborted (core dumped)
Found this one but doesn't seem like it's fixed on 15.10:
https://bugzilla.gnome.org/show_bug.cgi?id=748248
https://bugzilla.gnome.org/show_bug.cgi?id=748629
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1512521/+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 1512520] [NEW] New upstream release wpa 2.5
Public bug reported: Upstream release 2.5 has come out recently, including a number of security bugfixes and additional channel selection and performance improvements to 5GHz networks. Please update to it :) Changelog: 2015-09-27 - v2.5 * fixed P2P validation of SSID element length before copying it [http://w1.fi/security/2015-1/] (CVE-2015-1863) * fixed WPS UPnP vulnerability with HTTP chunked transfer encoding [http://w1.fi/security/2015-2/] (CVE-2015-4141) * fixed WMM Action frame parser (AP mode) [http://w1.fi/security/2015-3/] (CVE-2015-4142) * fixed EAP-pwd peer missing payload length validation [http://w1.fi/security/2015-4/] (CVE-2015-4143, CVE-2015-4144, CVE-2015-4145, CVE-2015-4146) * fixed validation of WPS and P2P NFC NDEF record payload length [http://w1.fi/security/2015-5/] * nl80211: - added VHT configuration for IBSS - fixed vendor command handling to check OUI properly - allow driver-based roaming to change ESS * added AVG_BEACON_RSSI to SIGNAL_POLL output * wpa_cli: added tab completion for number of commands * removed unmaintained and not yet completed SChannel/CryptoAPI support * modified Extended Capabilities element use in Probe Request frames to include all cases if any of the values are non-zero * added support for dynamically creating/removing a virtual interface with interface_add/interface_remove * added support for hashed password (NtHash) in EAP-pwd peer * added support for memory-only PSK/passphrase (mem_only_psk=1 and CTRL-REQ/RSP-PSK_PASSPHRASE) * P2P - optimize scan frequencies list when re-joining a persistent group - fixed number of sequences with nl80211 P2P Device interface - added operating class 125 for P2P use cases (this allows 5 GHz channels 161 and 169 to be used if they are enabled in the current regulatory domain) - number of fixes to P2PS functionality - do not allow 40 MHz co-ex PRI/SEC switch to force MCC - extended support for preferred channel listing * D-Bus: - fixed WPS property of fi.w1.wpa_supplicant1.BSS interface - fixed PresenceRequest to use group interface - added new signals: FindStopped, WPS pbc-overlap, GroupFormationFailure, WPS timeout, InvitationReceived - added new methods: WPS Cancel, P2P Cancel, Reconnect, RemoveClient - added manufacturer info * added EAP-EKE peer support for deriving Session-Id * added wps_priority configuration parameter to set the default priority for all network profiles added by WPS * added support to request a scan with specific SSIDs with the SCAN command (optional "ssid " arguments) * removed support for WEP40/WEP104 as a group cipher with WPA/WPA2 * fixed SAE group selection in an error case * modified SAE routines to be more robust and PWE generation to be stronger against timing attacks * added support for Brainpool Elliptic Curves with SAE * added support for CCMP-256 and GCMP-256 as group ciphers with FT * fixed BSS selection based on estimated throughput * added option to disable TLSv1.0 with OpenSSL (phase1="tls_disable_tlsv1_0=1") * added Fast Session Transfer (FST) module * fixed OpenSSL PKCS#12 extra certificate handling * fixed key derivation for Suite B 192-bit AKM (this breaks compatibility with the earlier version) * added RSN IE to Mesh Peering Open/Confirm frames * number of small fixes ** Affects: wpa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1512520 Title: New upstream release wpa 2.5 Status in wpa package in Ubuntu: New Bug description: Upstream release 2.5 has come out recently, including a number of security bugfixes and additional channel selection and performance improvements to 5GHz networks. Please update to it :) Changelog: 2015-09-27 - v2.5 * fixed P2P validation of SSID element length before copying it [http://w1.fi/security/2015-1/] (CVE-2015-1863) * fixed WPS UPnP vulnerability with HTTP chunked transfer encoding [http://w1.fi/security/2015-2/] (CVE-2015-4141) * fixed WMM Action frame parser (AP mode) [http://w1.fi/security/2015-3/] (CVE-2015-4142) * fixed EAP-pwd peer missing payload length validation [http://w1.fi/security/2015-4/] (CVE-2015-4143, CVE-2015-4144, CVE-2015-4145, CVE-2015-4146) * fixed validation of WPS and P2P NFC NDEF record payload length
[Desktop-packages] [Bug 1512521] [NEW] gvfs-trash fails on file in a symbolic linked folder in a different file system
Public bug reported:
I have Documents in a LUKS container mounted and symlinked on my home folder.
|-- Documents -> secure/documents
Have other folders like Desktop in a ecryptfs folder mounted and symlinked on
my home folder.
|-- Desktop -> Private/Desktop
So when I delete a file on Desktop or Documents it fails. It seems like it's
saving the file in .local/share/trash instead of inside the containers. I was
using fedora 22 and it was working fine. Now moved to ubuntu 15.10 and doesn't
seem to work.
strace of trying to delete the file:
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/gvfs/modules",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
lstat("/home/zed/Documents/secure-trash.txt", {st_mode=S_IFREG|0664, st_size=0,
...}) = 0
stat("/home/zed", {st_mode=S_IFDIR|0700, st_size=894, ...}) = 0
lstat("/home/zed/Documents", {st_mode=S_IFLNK|0777, st_size=16, ...}) = 0
access("/home", F_OK) = 0
stat("/home", {st_mode=S_IFDIR|0755, st_size=50, ...}) = 0
access("/home/zed", F_OK) = 0
stat("/home/zed", {st_mode=S_IFDIR|0700, st_size=894, ...}) = 0
access("/home/zed/.local", F_OK) = 0
stat("/home/zed/.local", {st_mode=S_IFDIR|0700, st_size=10, ...}) = 0
access("/home/zed/.local/share", F_OK) = 0
stat("/home/zed/.local/share", {st_mode=S_IFDIR|0700, st_size=224, ...}) = 0
access("/home/zed/.local/share/Trash", F_OK) = 0
stat("/home/zed/.local/share/Trash", {st_mode=S_IFDIR|0700, st_size=34, ...}) = 0
mkdir("/home/zed/.local/share/Trash/info", 0700) = -1 EEXIST (File exists)
mkdir("/home/zed/.local/share/Trash/files", 0700) = -1 EEXIST (File exists)
open("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo",
O_RDONLY|O_CREAT|O_EXCL, 0666) = 3
close(3)= 0
open("/etc/localtime", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=3687, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=3687, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7feb9f31b000
read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10\0\0\0\0"...,
4096) = 3687
lseek(3, -2347, SEEK_CUR) = 1340
read(3, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10\0\0\0\0"...,
4096) = 2347
close(3)= 0
munmap(0x7feb9f31b000, 4096)= 0
open("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo.DITD7X",
O_RDWR|O_CREAT|O_EXCL, 0666) = 3
fallocate(3, 0, 0, 94) = 0
write(3, "[Trash Info]\nPath=/home/bpmarinh"..., 94) = 94
fstatfs(3, {f_type=0x9123683e, f_bsize=4096, f_blocks=119953152,
f_bfree=76651779, f_bavail=76103891, f_files=0, f_ffree=0, f_fsid={-810601384,
-1547478495}, f_namelen=255, f_frsize=4096}) = 0
close(3)= 0
rename("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo.DITD7X",
"/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo") = 0
rename("/home/zed/Documents/secure-trash.txt",
"/home/zed/.local/share/Trash/files/secure-trash.txt") = -1 EXDEV (Invalid
cross-device link)
unlink("/home/zed/.local/share/Trash/info/secure-trash.txt.trashinfo") = 0
open("/dev/tty", O_RDWR|O_NOCTTY|O_NONBLOCK) = 3
writev(3, [{"*** Error in `", 14}, {"gvfs-trash", 10}, {"': ", 3}, {"double
free or corruption (fastt"..., 35}, {": 0x", 4}, {"01222aa0", 16}, {"
***\n", 5}], 7*** Error in `gvfs-trash': double free or corruption (fasttop):
0x01222aa0 ***
) = 87
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7feb9f31b000
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(5432, 5432, SIGABRT) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=5432, si_uid=1000} ---
+++ killed by SIGABRT (core dumped) +++
Aborted (core dumped)
Found this one but doesn't seem like it's fixed on 15.10:
https://bugzilla.gnome.org/show_bug.cgi?id=748248
https://bugzilla.gnome.org/show_bug.cgi?id=748629
** Affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Package changed: gnome-vfs (Ubuntu) => gvfs (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-vfs in Ubuntu.
https://bugs.launchpad.net/bugs/1512521
Title:
gvfs-trash fails on file in a symbolic linked folder in a different
file system
Status in gvfs package in Ubuntu:
New
Bug description:
I have Documents in a LUKS container mounted and symlinked on my home folder.
|-- Documents -> secure/documents
Have other folders like Desktop in a ecryptfs folder mounted and symlinked on
my home folder.
|-- Desktop -> Private/Desktop
So when I delete a file on Desktop or Documents it fails. It seems like it's
saving the file in .local/share/trash instead of inside the containers. I was
using fedora 22 and it was working fine. Now moved to ubuntu 15.10 and doesn't
seem to work.
strace of trying to delete the file:
openat(AT_FDCWD, "/usr/lib/x86_
[Desktop-packages] [Bug 1459143] Re: Complete system freeze upon switching WiFi networks
This issue hasn't affected me either since upgrading to 15.10. -- 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/1459143 Title: Complete system freeze upon switching WiFi networks Status in network-manager package in Ubuntu: Confirmed Bug description: Occasionally when I am manually switching from one WiFi network to another through the Indicator applet, the entire system freezes completely—neither the laptop's own keyboard and trackpad nor any USB devices produce any effect. The only way to resolve the situation is then to force a power down, which has caused me to lose data on several occasions. This started occurring on Xubuntu 15.04; I have not had any similar bugs on previous iterations of Xubuntu or other Ubuntu variants. It seems to happen when I am switching from an unsecured to a particular WPA-secured WiFi network, though as it happens only once in a while (about once every two days or so under moderate computer use) I am not sure about the source of the issue. I do know that it seems to happen only while switching WiFi networks. This is one of two new network-manager bugs that I noticed around the same time, immediately after upgrading to 15.04. The other bug was https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1270257. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1459143/+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 1512509] Re: slaac via pppoe fails with sif6addr failed
** Description changed: trying to configure ppp0 via SLAAC by adding +ipv6 ipv6 ,::3 and increasing the debug level, i find in the logs: Nov 2 23:03:37 zotac01 pppd[3796]: cif6addr: ioctl(SIOCDIFADDR): No such address Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr: ioctl(SIOCADDRT): File exists (line 2607) Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr failed Nov 2 23:03:37 zotac01 pppd[3796]: sent [IPV6CP TermReq id=0x2 "Interface configuration failed"] ppp0 has two ipv6 ips, both local, old ip remains linked no default route is received several IPV6CP ConfReq appear in the log not changing any parametr of the link a further configuration of the interface via dhcp is not possible because the interface never becomes able to transmit ipv6 packages. - reads like https://bugs.debian.org/cgi- - bin/bugreport.cgi?att=0;msg=10;bug=432728 + reads like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432728 i'm using pppd 2.4.5-5.1ubuntu2.2 source: https://launchpad.net/ubuntu/+source/ppp/2.4.5-5.1ubuntu2.2 - lsb_release -rd: Description: Ubuntu 14.04.3 LTS Release: 14.04 cheers, /markus -- 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/1512509 Title: slaac via pppoe fails with sif6addr failed Status in ppp package in Ubuntu: New Bug description: trying to configure ppp0 via SLAAC by adding +ipv6 ipv6 ,::3 and increasing the debug level, i find in the logs: Nov 2 23:03:37 zotac01 pppd[3796]: cif6addr: ioctl(SIOCDIFADDR): No such address Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr: ioctl(SIOCADDRT): File exists (line 2607) Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr failed Nov 2 23:03:37 zotac01 pppd[3796]: sent [IPV6CP TermReq id=0x2 "Interface configuration failed"] ppp0 has two ipv6 ips, both local, old ip remains linked no default route is received several IPV6CP ConfReq appear in the log not changing any parametr of the link a further configuration of the interface via dhcp is not possible because the interface never becomes able to transmit ipv6 packages. reads like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432728 i'm using pppd 2.4.5-5.1ubuntu2.2 source: https://launchpad.net/ubuntu/+source/ppp/2.4.5-5.1ubuntu2.2 lsb_release -rd: Description: Ubuntu 14.04.3 LTS Release: 14.04 cheers, /markus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1512509/+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 1475633] Re: New upstream version 2.4 / please merge with Debian 8's wpa 2.3
Thanks for the answer. Upstream has since released wpa 2.5 which includes those patches so I'll open a new request asking for that version instead of the backport. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1475633 Title: New upstream version 2.4 / please merge with Debian 8's wpa 2.3 Status in wpa package in Ubuntu: Fix Released Bug description: There are new wpa_supplicant versions 2.2, 2.3 and 2.4 which bring a horde of improvements to eg WiFi Direct (P2P) and others: http://w1.fi/cgit/hostap/plain/wpa_supplicant/ChangeLog The 2.3 is already part of the stable Debian 8.0 release so it would be useful to sync with at least that for 15.10 (and 16.04 LTS). --- Debian stable changelog --- wpa (2.3-1+deb8u1) jessie-security; urgency=high . * import "P2P: Validate SSID element length before copying it (CVE-2015-1863)" from upstream (Closes: #783148). wpa (2.3-1) unstable; urgency=medium . * New upstream release: - fixed by the new upstream version: + wpa: arbitrary command execution via action scripts (Closes: #765352). wpasupplicant: fixed wpa_cli action script execution to use more robust mechanism (CVE-2014-3686). hostapd: fixed hostapd_cli action script execution to use more robust mechanism (CVE-2014-3686). + wpasupplicant: MAC addressing changing broken after updating to 2.2-1 (Closes: #763775). + drop ap_config_c_fix-typo-for-capabilities, applied upstream. - backport "Include ieee802_11_common.c in wpa_supplicant build unconditionally" from HEAD, to fix a newly introduced FTBS on, at least, kfreebsd. * bump standards version to 3.9.6, no changes necessary. wpa (2.2-1) unstable; urgency=medium . * New upstream release: - import suggested changes from Gerald Turner (see #718651 for details). + disable ACS for hostapd on kfreebsd-any (FTBS). - fixed by the new upstream version: + wpa_supplicant: OpenSSL: tls_connection_handshake - Failed to read (Closes: #561081). + wpasupplicant: new upstream release 2.2 (Closes: #718651). + wpasupplicant: -s option not documented in man page (Closes: #608135). - refresh patches: + drop 13_human_readable_signal.patch, applied upstream. + drop hostapd_fix-WDS-VLAN-bridge-handling.patch, applied upstream. + drop fix-spelling-s-algorith-algorithm.patch, applied upstream. - adapt build configs for hostapd/ wpa_supplicant 2.2: + sync with updated upstream defconfigs. + keep Hotspot 2.0 support disabled for the time being. + hostapd: keep sqlite3 support disabled for the time being. - update debian/copyright manually, the wpa v2 branch was relicensed from (BSD-3-clause || GPL-2) to BSD-3-clause only (for the most part). This doesn't change the licensing state as the BSD-3-clause license is compatible with GPL-2. * drop pre-wheezy /lib/init/rw/sendsigs.omit.d/ migration support, invert the versioned initscripts dependency to a versioned breaks relation. * migrate from /var/run/ to /run/. * adapt get-orig-source for wpa 2.2. * drop version qualifiers for libnl3 build dependencies, as they're fullfilled by wheezy. * drop version qualifiers for the lsb-base build dependency, as they're fullfilled by squeeze. * shorten short description for hostapd. * sort debian/control entries. * make lintian happy (invalid-short-name-in-dep5-copyright bsd) and call it BSD-3-clause. * enable DEBUG_SYSLOG and set DEBUG_SYSLOG_FACILITY=LOG_DAEMON, as requested by Cyril Brulebois to improve logging options for d-i and netcfg (Closes: #761922). * fix various typos around "existence", thanks to A. Costa , (Closes: #683636). * ap_config.c: fix typo for "capabilities". * remove no longer required lintian override (spelling-error-in-binary for the). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1475633/+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 1512509] [NEW] slaac via pppoe fails with sif6addr failed
Public bug reported: trying to configure ppp0 via SLAAC by adding +ipv6 ipv6 ,::3 and increasing the debug level, i find in the logs: Nov 2 23:03:37 zotac01 pppd[3796]: cif6addr: ioctl(SIOCDIFADDR): No such address Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr: ioctl(SIOCADDRT): File exists (line 2607) Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr failed Nov 2 23:03:37 zotac01 pppd[3796]: sent [IPV6CP TermReq id=0x2 "Interface configuration failed"] ppp0 has two ipv6 ips, both local, old ip remains linked no default route is received several IPV6CP ConfReq appear in the log not changing any parametr of the link a further configuration of the interface via dhcp is not possible because the interface never becomes able to transmit ipv6 packages. reads like https://bugs.debian.org/cgi- bin/bugreport.cgi?att=0;msg=10;bug=432728 i'm using pppd 2.4.5-5.1ubuntu2.2 source: https://launchpad.net/ubuntu/+source/ppp/2.4.5-5.1ubuntu2.2 lsb_release -rd: Description:Ubuntu 14.04.3 LTS Release:14.04 cheers, /markus ** Affects: ppp (Ubuntu) Importance: Undecided Status: New -- 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/1512509 Title: slaac via pppoe fails with sif6addr failed Status in ppp package in Ubuntu: New Bug description: trying to configure ppp0 via SLAAC by adding +ipv6 ipv6 ,::3 and increasing the debug level, i find in the logs: Nov 2 23:03:37 zotac01 pppd[3796]: cif6addr: ioctl(SIOCDIFADDR): No such address Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr: ioctl(SIOCADDRT): File exists (line 2607) Nov 2 23:03:37 zotac01 pppd[3796]: sif6addr failed Nov 2 23:03:37 zotac01 pppd[3796]: sent [IPV6CP TermReq id=0x2 "Interface configuration failed"] ppp0 has two ipv6 ips, both local, old ip remains linked no default route is received several IPV6CP ConfReq appear in the log not changing any parametr of the link a further configuration of the interface via dhcp is not possible because the interface never becomes able to transmit ipv6 packages. reads like https://bugs.debian.org/cgi- bin/bugreport.cgi?att=0;msg=10;bug=432728 i'm using pppd 2.4.5-5.1ubuntu2.2 source: https://launchpad.net/ubuntu/+source/ppp/2.4.5-5.1ubuntu2.2 lsb_release -rd: Description: Ubuntu 14.04.3 LTS Release: 14.04 cheers, /markus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1512509/+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 1512502] [NEW] Release no-change rebuild for ocaml transition
Public bug reported: The llvm-toolchain-3.5 package needs a no-change rebuild for the ocaml transition. See attached debdiff for details. Thank you! ** Affects: llvm-toolchain-3.5 (Ubuntu) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: In Progress ** Patch added: "No-change rebuild debdiff" https://bugs.launchpad.net/bugs/1512502/+attachment/4511558/+files/llvm-toolchain-3.5_3.5.2-3build1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.5 in Ubuntu. https://bugs.launchpad.net/bugs/1512502 Title: Release no-change rebuild for ocaml transition Status in llvm-toolchain-3.5 package in Ubuntu: In Progress Bug description: The llvm-toolchain-3.5 package needs a no-change rebuild for the ocaml transition. See attached debdiff for details. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1512502/+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 1286102] Re: Error "Extension Manager: exception in synchronize" on LibreOffice startup
OOps forgot to tell what directory: it is /usr/lib/libreoffice/share/uno_packages/cache/uno_package -- 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/1286102 Title: Error "Extension Manager: exception in synchronize" on LibreOffice startup Status in libreoffice package in Ubuntu: Invalid Bug description: I'm using Ubuntu 14.04 dev with libreoffice-core 1:4.2.1-0ubuntu1 and on starting any LibreOffice application (for example calc or writer) LibreOffice will show the following error at the loading process: "The application cannot be started. Extension Manager: exception in synchronize" On clicking on OK LibreOffice will then exit immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1286102/+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 828684] Re: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
** Bug watch removed: Debian Bug tracker #627372 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 ** Bug watch removed: freedesktop.org Bugzilla #41091 https://bugs.freedesktop.org/show_bug.cgi?id=41091 ** Bug watch removed: freedesktop.org Bugzilla #49041 https://bugs.freedesktop.org/show_bug.cgi?id=49041 -- 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/828684 Title: [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: [Problem] The Intel driver experiences a GPU hang, but is able to recover from it automatically. The user does not see any sort of bug/crash/lockup symptom, however the error handler does detect the GPU hang and triggers the crash report dialog. In some cases this occurs during boot, so that the error dialog appears immediately after logging in. In other cases this occurs while using the system, so an error dialog pops up "out of nowhere" (or perhaps on the next boot). [Unrelated Issues] If your system actually does experience a lock up (screen unresponsive and perhaps black, but the mouse cursor might still move), you have a real GPU lockup and should not link to this bug. These lockups could appear randomly during use, or in relation to booting, shutting down, sleep/resume, or other specific X activity. If you have a specific symptom that you believe is correlated or associated with the error dialog, do not dupe to this bug report. The error message says, ' Sorry, the program "apport-gpu-error- intel.py" closed unexpectly ... ' but in truth it wasn't the named python script that failed. The prompt should say "Sorry, the GPU appears to have hung unexpectedly..." But that issue will be handled separately. If you do believe you have found a scripting error in apport-gpu-error-intel.py, that should be filed separately. [From a dupe] """ Seem to detect this bug after system hangs going into shutdown. Has been happening on and off to me since I upgraded to 11.10 testing (Oneiric) . On reboot "Application problem" dialogs open reporting the following: ' Sorry, the program "apport-gpu-error-intel.py" closed unexpectly ... ' """ ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic i686 NonfreeKernelModules: wl Architecture: i386 BootLog: fsck from util-linux 2.19.1 /dev/sda5: clean, 161626/586368 files, 808322/2342773 blocks Chipset: i965gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDmesg: [ 20.630556] Bluetooth: BNEP filters: protocol multicast [ 20.669359] Bluetooth: RFCOMM TTY layer initialized [ 20.669364] Bluetooth: RFCOMM socket layer initialized [ 20.669366] Bluetooth: RFCOMM ver 1.11 Date: Thu Aug 18 12:37:18 2011 DistUpgraded: Log time: 2011-08-17 20:01:20.326261 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.38+bdcom, 3.0.0-7-generic, i686: installed bcmwl, 5.100.82.38+bdcom, 3.0.0-8-generic, i686: installed DuplicateSignature: [i965gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 Ubuntu 11.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Computer Inc. Device [106b:00a1] Subsystem: Apple Computer Inc. Device [106b:00a1] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1) InterpreterPath: /usr/bin/python2.7 MachineType: Apple Inc. MacBook3,1 ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic root=UUID=a0375c54-0bf7-41d1-88c8-503a02134def ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+7ubuntu6 libdrm2 2.4.26-1ubuntu1 xserver-xorg-video-intel 2:2.15.901-1ubuntu2 SourcePackage: xserver-xorg-video-intel Title: [i965gm] False GPU lockup EIR: 0x0010 PGTBL_ER: 0x0100 UpgradeStatus: Upgraded to oneiric on 2011-08-17 (0 days ago) UserGroups: dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB31.88Z.008E.B02.0803051832 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788C8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB31.88Z
[Desktop-packages] [Bug 1286102] Re: Error "Extension Manager: exception in synchronize" on LibreOffice startup
Very strange, I just found a directory that was setted 750 as mode, changed it to 755 : the bug disapear. To confirm, I got back the dir mode to 750, the bug doesn't occur anymore. In doubt, I leave it setted to 755 as it shouldn't hurt but I do not understand what does the trick. Hope this help ;) -- 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/1286102 Title: Error "Extension Manager: exception in synchronize" on LibreOffice startup Status in libreoffice package in Ubuntu: Invalid Bug description: I'm using Ubuntu 14.04 dev with libreoffice-core 1:4.2.1-0ubuntu1 and on starting any LibreOffice application (for example calc or writer) LibreOffice will show the following error at the loading process: "The application cannot be started. Extension Manager: exception in synchronize" On clicking on OK LibreOffice will then exit immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1286102/+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 1097965] Re: shutdown while stille 50min battery
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1097965 Title: shutdown while stille 50min battery Status in upower package in Ubuntu: Confirmed Bug description: The indicator claims still 50+min of available battery but suddently system executes the shutdown ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upower 0.9.15-3git1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 NonfreeKernelModules: nvidia wl ApportVersion: 2.0.1-0ubuntu15.1 Architecture: i386 Date: Wed Jan 9 23:09:28 2013 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MarkForUpload: True SourcePackage: upower UpgradeStatus: Upgraded to precise on 2012-06-09 (214 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1097965/+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 1286102] Re: Error "Extension Manager: exception in synchronize" on LibreOffice startup
If it may help, here is a calls trace
/home/phl$ strace localc
execve("/usr/bin/localc", ["localc"], [/* 42 vars */]) = 0
brk(0) = 0x7fbf9c282000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbf9aae6000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=105917, ...}) = 0
mmap(NULL, 105917, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbf9aacc000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1729984, ...}) = 0
mmap(NULL, 3836448, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fbf9a301000
mprotect(0x7fbf9a4a, 2097152, PROT_NONE) = 0
mmap(0x7fbf9a6a, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19f000) = 0x7fbf9a6a
mmap(0x7fbf9a6a6000, 14880, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbf9a6a6000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbf9aacb000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbf9aaca000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbf9aac9000
arch_prctl(ARCH_SET_FS, 0x7fbf9aaca700) = 0
mprotect(0x7fbf9a6a, 16384, PROT_READ) = 0
mprotect(0x7fbf9aae8000, 12288, PROT_READ) = 0
mprotect(0x7fbf9a8ca000, 4096, PROT_READ) = 0
munmap(0x7fbf9aacc000, 105917) = 0
getpid()= 28479
rt_sigaction(SIGCHLD, {0x7fbf9a8defd0, ~[RTMIN RT_1], SA_RESTORER,
0x7fbf9a336180}, NULL, 8) = 0
geteuid() = 1000
brk(0) = 0x7fbf9c282000
brk(0x7fbf9c2a3000) = 0x7fbf9c2a3000
getppid() = 28476
stat("/usr/lib/libreoffice/share/extensions", {st_mode=S_IFDIR|0755,
st_size=4096, ...}) = 0
stat(".", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/bin/localc", O_RDONLY) = 3
fcntl(3, F_DUPFD, 10) = 10
close(3)= 0
fcntl(10, F_SETFD, FD_CLOEXEC) = 0
rt_sigaction(SIGINT, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGINT, {0x7fbf9a8defd0, ~[RTMIN RT_1], SA_RESTORER,
0x7fbf9a336180}, NULL, 8) = 0
rt_sigaction(SIGQUIT, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL, ~[RTMIN RT_1], SA_RESTORER, 0x7fbf9a336180},
NULL, 8) = 0
rt_sigaction(SIGTERM, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGTERM, {SIG_DFL, ~[RTMIN RT_1], SA_RESTORER, 0x7fbf9a336180},
NULL, 8) = 0
read(10, "#!/bin/sh\n/usr/lib/libreoffice/p"..., 8192) = 59
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7fbf9aaca9d0) = 28480
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 77}], 0, NULL) = 28480
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=28480, si_uid=1000,
si_status=77, si_utime=0, si_stime=0} ---
rt_sigreturn() = 28480
read(10, "", 8192) = 0
exit_group(77) = ?
+++ exited with 77 +++
--
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/1286102
Title:
Error "Extension Manager: exception in synchronize" on LibreOffice
startup
Status in libreoffice package in Ubuntu:
Invalid
Bug description:
I'm using Ubuntu 14.04 dev with libreoffice-core 1:4.2.1-0ubuntu1 and
on starting any LibreOffice application (for example calc or writer)
LibreOffice will show the following error at the loading process:
"The application cannot be started.
Extension Manager: exception in synchronize"
On clicking on OK LibreOffice will then exit immediately.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1286102/+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 1286102] Re: Error "Extension Manager: exception in synchronize" on LibreOffice startup
indefinitely waits at last line after: wait4(-1, so need to break it -- 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/1286102 Title: Error "Extension Manager: exception in synchronize" on LibreOffice startup Status in libreoffice package in Ubuntu: Invalid Bug description: I'm using Ubuntu 14.04 dev with libreoffice-core 1:4.2.1-0ubuntu1 and on starting any LibreOffice application (for example calc or writer) LibreOffice will show the following error at the loading process: "The application cannot be started. Extension Manager: exception in synchronize" On clicking on OK LibreOffice will then exit immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1286102/+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 1510180] Re: Xorg freeze
thx!!! I've updated my BIOS. So far I've had a few crashes ... but it wasn't clear if it's not due to my new mt7601Usta patched wifi-driver ... usb wifi stick ... If I see the patterned screen with full freeze again I'll send another bug report ... If not, I'll give it a few days and change the bug-report status (if I don't forget) ... thx, J +--[ RSA 2048]+ | . | | . . o | | . o + | | . = . | |S = E o| | o + * o.| | o @ + | | + * | |... | +-+ +--+ |tn?bo | |i-?* | |+c1 | |=?| |f # ## | | # #| | # ## | |# ## | | ## ## | +--+ jsstyle.github.com 2015-11-01 11:53 GMT-04:00 Christopher M. Penalver < christopher.m.penal...@gmail.com>: > Dipl.-Ing. (FH) Johannes Neugschwentner, thank you for reporting this > and helping make Ubuntu better. > > As per https://www.asus.com/Motherboards/H97IPLUS/HelpDesk_Download/ an > update to your computer's buggy and outdated BIOS is available (2604). > If you update to this following > https://help.ubuntu.com/community/BIOSUpdate does it change anything? > > If it doesn't, could you please both specify what happened, and provide > the output of the following terminal command: > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date > > For more on BIOS updates and linux, please see > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > . > > Please note your current BIOS is already in the Bug Description, so > posting this on the old BIOS would not be helpful. As well, you don't > have to create a new bug report. > > Once the BIOS is updated, if the problem is still reproducible, and the > information above is provided, then please mark this report Status New. > Otherwise, please mark this as Invalid. > > Thank you for your understanding. > > ** Tags added: bios-outdated-2604 > > ** 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/1510180 > > Title: > Xorg freeze > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > Neither the proprietery nor the open source driver work well for my > ATI graphics card. > > The OS driver is the better choice, as it crashes about twice a day and > that's it ... > Crashes = strange patterns filling the screen plus X crashing (Keyboard > combinations don't have effect anymore I think ... tried to quit my code > editor with alt+f4 which should have closed all sourcefiles I was working > on, still some of them were scrambled after reboot) > > The proprietary driver works well for some time, then brings on all > kinds of artifacts, displaying old (buffered) parts of windows where they > aren't etc., for example on mouse scrolling ... unusable really > The Troubleshooting guide says something to check and by trial n error > fix this in the BIOS by trying all AGP APERTURE SIZE settings ... well, I > ain't got no AGP, I got the new stuff (ahemmm ... forget the name ...) > Also, I read it doesn't work with the new kernel of Ubuntu Wily ... so I > guess I'm in luck I switched back in time. > > ProblemType: Bug > DistroRelease: Ubuntu 15.10 > Package: xorg 1:7.7+7ubuntu4 > ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3 > Uname: Linux 4.2.0-16-lowlatency x86_64 > .tmp.unity.support.test.0: > > ApportVersion: 2.19.1-0ubuntu3 > Architecture: amd64 > CompizPlugins: > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Mon Oct 26 12:42:14 2015 > DistUpgraded: 2015-10-23 23:59:32,729 DEBUG enabling apt cron job > DistroCodename: wily > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GpuHangFrequency: Several times a day > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Since before I upgraded > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] > [1002:6658] (prog-if 00 [VGA controller]) > Subsystem: XFX Pine Group Inc. Device [1682:7260] > InstallationDate: Installed on 2014-11-21 (338 days ago) > InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Release amd64 > (20141022.2) > MachineType: ASUS All Series > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-lowlatency > root=UUID=72fb5ab9-1811-4038-a327-f02734b8adbb ro quiet splash vt.handoff=7 > SourcePackage:
[Desktop-packages] [Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10
I can reproduce this consistently by opening up a calendar event in Thunderbird. I also could reproduce this consistently when I opened up a chat log dialog in Pidgin - but I could work around it by disabling animations via CompizConfigSettingsManager. @Johannes, you could try that work around, but yes, please fix this. I think booting into a different kernel fixes the problem, but I have things installed that depend on the latest kernel. -- 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/1510970 Title: Intel driver crashes on Ubuntu 15.10 Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before the update everything was stable. The problem occured mostly while using Thunderbird but also once while using Firefox. The Xserver crashes and I'm logged out. It takes about 10 seconds until gdm fires up again and I'm able to login again. The last part of /var/log/Xorg.0.log says: [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920 [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 1, position (0, 0), rotation left, reflection none [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1080, 406), rotation normal, reflection none [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 0, position (1080, 502), rotation normal, reflection none [ 20012.432] (EE) [ 20012.432] (EE) Backtrace: [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e] [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999] [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) [0x7fe7c65522f0] [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18] [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x26157) [0x7fe7c291a157] [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1] [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4] [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c] [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a] [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x4197c) [0x7fe7c293597c] [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fe7c28f4000+0x59906) [0x7fe7c294d906] [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654] [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274] [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502] [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a] [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5] [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f] [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b] [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fe7c653da40] [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9] [ 20012.433] (EE) [ 20012.433] (EE) Segmentation fault at address 0x0 [ 20012.433] (EE) Fatal server error: [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 20012.433] (EE) [ 20012.433] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 20012.433] (EE) [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch [ 20012.456] (EE) Server terminated with error (1). Closing log file. These parts of dmesg might be interesting: [1.661760] input: Logitech USB Keyboard as /devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8 [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1 [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder B [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder B FIFO underrun [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [2.586624] clocksource: Switched to clo
[Desktop-packages] [Bug 1512498] [NEW] gnome-terminal thinks it's Byobu Terminal
Public bug reported: After dist-upgrading from Wily to Xenial, gnome-terminal has a global menu bar entry, and switcher icon of Byobu Terminal. This is regardless of whether I start Terminal via gnome-do, unity (search or sidebar), or Emacs shell buffer typing 'gnome-terminal'. Other than that, I can't tell any difference from "traditional" gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 2 15:48:52 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-06 (696 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Summary changed: - gnome-terminal thinks its Byobu Terminal + gnome-terminal thinks it's Byobu Terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1512498 Title: gnome-terminal thinks it's Byobu Terminal Status in gnome-terminal package in Ubuntu: New Bug description: After dist-upgrading from Wily to Xenial, gnome-terminal has a global menu bar entry, and switcher icon of Byobu Terminal. This is regardless of whether I start Terminal via gnome-do, unity (search or sidebar), or Emacs shell buffer typing 'gnome-terminal'. Other than that, I can't tell any difference from "traditional" gnome-terminal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 2 15:48:52 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-06 (696 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1512498/+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 1286102] Re: Error "Extension Manager: exception in synchronize" on LibreOffice startup
I get this same bug running LO 4.3/debian 8.2 on Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) x86_64 GNU/Linux I don't use any extension. I recently update my Debian distro from 7.8 to 8.2 and there was no problem with Debian 7.8 This issue doesn't occur when LO is launched by root. (as far as I know, permissions are correct undder /usr/lib/libreoffice : owned root:root, mode 755 for dirs and executables files, 644 for other files) -- 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/1286102 Title: Error "Extension Manager: exception in synchronize" on LibreOffice startup Status in libreoffice package in Ubuntu: Invalid Bug description: I'm using Ubuntu 14.04 dev with libreoffice-core 1:4.2.1-0ubuntu1 and on starting any LibreOffice application (for example calc or writer) LibreOffice will show the following error at the loading process: "The application cannot be started. Extension Manager: exception in synchronize" On clicking on OK LibreOffice will then exit immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1286102/+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 1510998] Re: Xorg crashes with segfault on 15.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1510998 Title: Xorg crashes with segfault on 15.10 Status in xorg package in Ubuntu: Confirmed Bug description: I updated my system from 15.04 to 15.10 yesterday. Since then the X server has already crashed 5 times, which renders the system close to unusable for me. The corresponding messages in Xorg.0.log.old are: [ 12125.023] (EE) [ 12125.023] (EE) Backtrace: [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e] [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999] [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) [0x7f7c10eb02f0] [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x24edc) [0x7f7c0d276edc] [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x26157) [0x7f7c0d278157] [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8] [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec] [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x59103) [0x7f7c0d2ab103] [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa] [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73] [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3] [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f] [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b] [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f7c10e9ba40] [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9] [ 12125.023] (EE) [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0 [ 12125.023] (EE) Fatal server error: [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting I have attached the syslog file. The relevant messages for the three crashes from today can be found at: Oct 28 15:56:36 Oct 28 12:06:58 Oct 28 09:08:51 Unfortunately I have no clue how to reproduce the segfault. The last crash happened while I was reading some document and I did not push any button, moved the mouse or anything... ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Oct 28 16:30:43 2015 DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: kubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:091c] InstallationDate: Installed on 2015-01-20 (281 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon MachineType: Acer Aspire VN7-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-571G dmi.board.vendor: Acer dmi.board.version: V1.14 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1
[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with Chromium
also this is happening(convergence in action), I think is would be quite important to have netflix out of box on the convergence devices: https://plus.google.com/+ReinerKlenk/posts/5Jwzahxjxsw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1371274 Title: Unable to use the widevine plugin with Chromium Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium is unable to use the widevine component from google chrome : libwidevinecdmadapter.so and libwidevinecdm.so How to reproduce : - copy the 2 files the chrome archive in /usr/lib/chromium-browser - check chrome://components/ - Widevine does not appear Solution : With the help from several people (hogliux for patch and saiarcot895 for PPA) , a PPA is available with this feature : - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev - You need the binary widevine plugin plugin (2 files) : https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz To be copied in /usr/lib/chromium - Launch netflix.com and see if it works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042 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 Date: Thu Sep 18 21:11:17 2014 InstallationDate: Installed on 2013-10-02 (350 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 'system-image-cli' UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1371274/+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 1512099] Re: plugin-container crashed with SIGSEGV in mozalloc_abort()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1512099 Title: plugin-container crashed with SIGSEGV in mozalloc_abort() Status in firefox package in Ubuntu: New Bug description: Заебали ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: firefox 41.0.2+build2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.14.4-0ubuntu1~ubuntu14.04.1~c42.ppa1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1854 F pulseaudio BuildID: 20151015172906 Channel: Unavailable CurrentDesktop: XFCE Date: Sun Nov 1 16:00:57 2015 ExecutablePath: /usr/lib/firefox/plugin-container Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2015-09-30 (31 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) IpRoute: default via 10.10.10.1 dev eth1 proto static 10.10.10.0/24 dev eth1 proto kernel scope link src 10.10.10.3 metric 9 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-fe84bf0f-8087-40f8-8220-f33f62151004 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Java(TM) Plug-in 11.66.2 - /usr/lib/jvm/java-8-oracle/jre/lib/i386/libnpjp2.so PrefSources: prefs.js ProcCmdline: /usr/lib/firefox/plugin-container /usr/lib/flashplugin-installer/libflashplayer.so -greomni /usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir /usr/lib/firefox/browser 2277 plugin Profiles: Profile0 (Default) - LastVersion=41.0.2/20151015172906 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SegvAnalysis: Segfault happened at: 0xb774911e <_Z14mozalloc_abortPKc+58>: movl $0x21,0x0 PC (0xb774911e) ok source "$0x21" ok destination "0x0" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: firefox StacktraceTop: mozalloc_abort(char const*) () NS_DebugBreak () from /usr/lib/firefox/libxul.so ?? () from /usr/lib/firefox/libxul.so ?? () from /usr/lib/firefox/libxul.so ?? () from /usr/lib/firefox/libxul.so SubmittedCrashIDs: bp-fe84bf0f-8087-40f8-8220-f33f62151004 Themes: extensions.sqlite corrupt or missing Title: plugin-container crashed with SIGSEGV in mozalloc_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/28/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0WF351 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/28/2005:svnDellInc.:pnInspiron6000:pvr:rvnDellInc.:rn0WF351:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 6000 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1512099/+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 1453174] Re: Opening of magnet links broken
** Changed in: gvfs (Ubuntu Vivid) Status: Fix Committed => Fix Released -- 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/1453174 Title: Opening of magnet links broken Status in gvfs: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Vivid: Fix Released Bug description: * Impact some urls are not correctly handled * Test case $ xdg-open "magnet:?xt=urn:btih:9BE2..." that should open a working dialog and not an error one * Regression potential check that the desktop handling of urls is correct (using xdg-open or click on e.g in website handlers in about dialogs) --- When clicking on a magnet link, transmission-remote-gtk always displays the error "invalid or corrupt torrent file". This seems to be caused by xdg-open slightly modifying the link: $ xdg-open "magnet:?xt=urn:btih:9BE2..." results in $ transmission-remote-gtk "magnet:///?xt=urn:btih:9BE2..." which causes the problem mentioned. I'm using transmission-remote-gtk 1.1.1-1 from vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1453174/+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 1512467] Re: Release no-change rebuild for ocaml transition
Uploaded. ** Changed in: hevea (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hevea in Ubuntu. https://bugs.launchpad.net/bugs/1512467 Title: Release no-change rebuild for ocaml transition Status in hevea package in Ubuntu: Fix Released Bug description: The havea package needs to be no-change rebuilt for the ocaml transition. See attached debdiff for details. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hevea/+bug/1512467/+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 1511330] Re: PPTP connection does not establish due to something "did not receive a valid configuration"
After upgrading to VPN stopped working. I removed the static routes and VPN returned to work. Thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1511330 Title: PPTP connection does not establish due to something "did not receive a valid configuration" Status in network-manager-pptp package in Ubuntu: Confirmed Bug description: The PPTP connection in question used to work on Vivid, now it does not connect after an upgrade to Wily. The relevant piece of syslog follows: Oct 29 14:03:45 monkey-mafia NetworkManager[876]: Starting VPN service 'pptp'... Oct 29 14:03:45 monkey-mafia NetworkManager[876]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 7190 Oct 29 14:03:45 monkey-mafia NetworkManager[876]: VPN service 'pptp' appeared; activating connections Oct 29 14:03:45 monkey-mafia NetworkManager[876]: VPN connection 'Office PPTP' (ConnectInteractive) reply received. Oct 29 14:03:45 monkey-mafia NetworkManager[876]: VPN plugin state changed: starting (3) Oct 29 14:03:45 monkey-mafia NetworkManager[876]: ** Message: pppd started with pid 7195 Oct 29 14:03:45 monkey-mafia NetworkManager[876]: VPN connection 'Office PPTP' (Connect) reply received. Oct 29 14:03:45 monkey-mafia pppd[7195]: Plugin /usr/lib/pppd/2.4.6/nm-pptp-pppd-plugin.so loaded. Oct 29 14:03:45 monkey-mafia NetworkManager[876]: Plugin /usr/lib/pppd/2.4.6/nm-pptp-pppd-plugin.so loaded. Oct 29 14:03:45 monkey-mafia NetworkManager[876]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing Oct 29 14:03:45 monkey-mafia pppd[7195]: pppd 2.4.6 started by root, uid 0 Oct 29 14:03:45 monkey-mafia NetworkManager[876]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection' Oct 29 14:03:45 monkey-mafia pppd[7195]: Using interface ppp0 Oct 29 14:03:45 monkey-mafia pppd[7195]: Connect: ppp0 <--> /dev/pts/12 Oct 29 14:03:45 monkey-mafia NetworkManager[876]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Oct 29 14:03:45 monkey-mafia NetworkManager[876]: (ppp0): new Generic device (carrier: UNKNOWN, driver: 'unknown', ifindex: 8) Oct 29 14:03:45 monkey-mafia NetworkManager[876]: Using interface ppp0 Oct 29 14:03:45 monkey-mafia NetworkManager[876]: Connect: ppp0 <--> /dev/pts/12 Oct 29 14:03:45 monkey-mafia NetworkManager[876]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish' Oct 29 14:03:45 monkey-mafia pptp[7199]: nm-pptp-service-7190 log[main:pptp.c:350]: The synchronous pptp option is NOT activated Oct 29 14:03:45 monkey-mafia NetworkManager[876]: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Oct 29 14:03:45 monkey-mafia NetworkManager[876]: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Oct 29 14:03:46 monkey-mafia pptp[7217]: nm-pptp-service-7190 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 'Start-Control-Connection-Request' Oct 29 14:03:46 monkey-mafia pptp[7217]: nm-pptp-service-7190 log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply Oct 29 14:03:46 monkey-mafia pptp[7217]: nm-pptp-service-7190 log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established. Oct 29 14:03:47 monkey-mafia pptp[7217]: nm-pptp-service-7190 log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 7 'Outgoing-Call-Request' Oct 29 14:03:47 monkey-mafia pptp[7217]: nm-pptp-service-7190 log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply. Oct 29 14:03:47 monkey-mafia pptp[7217]: nm-pptp-service-7190 log[ctrlp_disp:pptp_ctrl.c:939]: Outgoing call established (call ID 43272, peer's call ID 251). Oct 29 14:03:47 monkey-mafia NetworkManager[876]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate' Oct 29 14:03:47 monkey-mafia NetworkManager[876]: ** Message: nm-pptp-ppp-plugin: (get_credentials): passwd-hook, requesting credentials... Oct 29 14:03:47 monkey-mafia NetworkManager[876]: ** Message: nm-pptp-ppp-plugin: (get_credentials): got credentials from NetworkManager-pptp Oct 29 14:03:47 monkey-mafia pppd[7195]: CHAP authentication succeeded Oct 29 14:03:47 monkey-mafia NetworkManager[876]: CHAP authentication succeeded Oct 29 14:03:47 monkey-mafia NetworkManager[876]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network' Oct 29 14:03:47 monkey-mafia pppd[7195]: MPPE 128-bit stateless compression enabled Oct 29 14:03:47 monkey-mafia NetworkManager[876]: MPPE 128-bit stateless compression enabled Oct 29 14:03:48 monkey-mafia pppd[7195]: local IP address 192.168.17.35 Oct 29 14:03:48 monkey-mafia pppd[7195]: remote IP address 192.168.17.1 Oct 29 14:03:48 monkey-mafia pppd[7195]: primary DNS address 192.168.17.1 Oct 29 14:03:48 mo
[Desktop-packages] [Bug 1453174] Re: Opening of magnet links broken
** Changed in: gvfs (Ubuntu Vivid) Importance: Undecided => High ** Tags added: vivid ** Also affects: gvfs via https://bugzilla.gnome.org/show_bug.cgi?id=738690 Importance: Unknown Status: Unknown -- 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/1453174 Title: Opening of magnet links broken Status in gvfs: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Vivid: Fix Committed Bug description: * Impact some urls are not correctly handled * Test case $ xdg-open "magnet:?xt=urn:btih:9BE2..." that should open a working dialog and not an error one * Regression potential check that the desktop handling of urls is correct (using xdg-open or click on e.g in website handlers in about dialogs) --- When clicking on a magnet link, transmission-remote-gtk always displays the error "invalid or corrupt torrent file". This seems to be caused by xdg-open slightly modifying the link: $ xdg-open "magnet:?xt=urn:btih:9BE2..." results in $ transmission-remote-gtk "magnet:///?xt=urn:btih:9BE2..." which causes the problem mentioned. I'm using transmission-remote-gtk 1.1.1-1 from vivid. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1453174/+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 253167] Re: Rhythmbox sort by "Album Artist" for guest/compilations
No bumping please, no complaining for heavens sake , no asking nicely - how dare you! Well 7 years of an open bug is not fixed because the devs do not understand the problem... Sure they have any right to not do anything about it. That's why I ditched rhythmbox years ago, just came around to check whether anything happens here... lol... I guessed so. Whatever the "upstream" procedure is here - obviously it doesn't help anyone. Great system of developing! And that's why we can't have nice things. You devs have done a great job 10 years ago, since then..., meh... not so much... Rhythmbox still feels 10 years old and users can not sort by album artist if they so desire - funny kind of freedom Cheers, p. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/253167 Title: Rhythmbox sort by "Album Artist" for guest/compilations Status in Rhythmbox: Confirmed Status in rhythmbox package in Ubuntu: Triaged Bug description: Binary package hint: rhythmbox For guest artists on an album or compilations Apple allows definition of an album artist and artist for each track. Rhythmnbox only allows browsing by track artists so many artists appear listed with only one track. Example, Red Book by Texas: 1. 036 - Texas 2. Getaway - Texas 3. Can't Resist - Texas 4. What About Us - Texas 5. Cry - Texas 6. Sleep - Texas featuring Paul Buchanan 7. Get Down Tonight - Texas 8. Nevermind - Texas 9. Bad Weather - Texas 10. Master Thief - Texas 11. Just Holding On - Texas 12. Red Book - Texas The sixth track has artist "Texas featuring Paul Buchanan" whilst all others are "Texas". I want to browse by album artist selecting "Texas" and seeing all 12 tracks on the album, not just the 11 that match. To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/253167/+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 1500516] Re: /usr/lib/gvfs/gvfs-udisks2-volume-monitor:11:g_type_check_instance_cast:unmount_operation_is_eject:unmount_data_complete:unmount_cb:g_simple_async_result_complete
** Changed in: gvfs (Ubuntu Vivid) Importance: Undecided => High -- 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/1500516 Title: /usr/lib/gvfs/gvfs-udisks2-volume- monitor:11:g_type_check_instance_cast:unmount_operation_is_eject:unmount_data_complete:unmount_cb:g_simple_async_result_complete Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Vivid: Fix Committed Bug description: * Impact the gvfs disk monitors segfaults sometimes * Test case no defined one, but the e.u.c reports should stop with the update * Regression potential check if disks and external storage devices are still correctly handled (listed in the launcher, included in nautilus, etc) - The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with version 1.24.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/5d8e0bd14d691af888168ae3ff6a80e7fa95ebf4 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1500516/+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 1175947] Re: gvfs-copy --preserve doesn't work with MTP devices
** Tags added: raring vivid ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low ** Changed in: gvfs (Ubuntu Vivid) Importance: Undecided => Low ** Changed in: gvfs (Ubuntu Vivid) Status: New => Fix Committed ** Tags added: trusty ** Bug watch removed: code.google.com/p/android/issues #18624 http://code.google.com/p/android/issues/detail?id=18624 ** Description changed: - * Impact - When using gvfs-copy --preserve from a MTP device to local, the timestamp is not preserved. + [Impact] - touch "localfile" --reference="MTP file" works ok. - I assume --preserve is not working. + * When using gvfs-copy --preserve from a MTP device to local, the timestamp + is not preserved. - * Test case - copy files from a mtp device using the --preserve option and check timestamps + * touch "localfile" --reference="MTP file" works OK. - * Regression potential - verify files copied from mtp devices and their attributes + * I assume --preserve is not working. + + [Test Case] + + * Copy files from a MTP device using the --preserve option and check + timestamps. + + [Regression Potential] + + * Verify files copied from MTP devices and their attributes. -- 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/1175947 Title: gvfs-copy --preserve doesn't work with MTP devices Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Vivid: Fix Committed Bug description: [Impact] * When using gvfs-copy --preserve from a MTP device to local, the timestamp is not preserved. * touch "localfile" --reference="MTP file" works OK. * I assume --preserve is not working. [Test Case] * Copy files from a MTP device using the --preserve option and check timestamps. [Regression Potential] * Verify files copied from MTP devices and their attributes. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1175947/+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 1512435] Re: Stop depending on gnome-control-center
** Tags added: patch -- 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/1512435 Title: Stop depending on gnome-control-center Status in unity-control-center package in Ubuntu: In Progress Bug description: Currently u-c-c depends on g-c-c-shared-data that prevents that one to be moved to universe. The shared data include 2 things - some image to be used for user accounts - some polkit rules the image are small, we could copy them in u-c-c, the polkit rules could be included in the desktop profile instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1512435/+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 1505328] Re: Cups SSL is vulernable to POODLE
The attachment "now current debdiff (fixes accidentally included file)" 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.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1505328 Title: Cups SSL is vulernable to POODLE Status in cups package in Ubuntu: New Bug description: On 12.04 and 14.04 if you enable cups ssl you are vulnerable to poodle, and there does not appear to be any way to mitigate it in Cups config. Ubuntu 14.04 - https://www.ssllabs.com/ssltest/analyze.html?d=190.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on Ubuntu 12.04 - https://www.ssllabs.com/ssltest/analyze.html?d=191.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on Fixed in wily - https://www.ssllabs.com/ssltest/analyze.html?d=192.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on Upstream fix - https://www.cups.org/str.php?L4476 Should we disable ssvl3 in the 12.04/14.04 cups by default and backport the option to turn it back on? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1505328/+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 1511674] Re: Memory leak
A memory leak has been fixed in pcsc-lite 1.8.12 Can you install a newer version of pcscd (http://packages.ubuntu.com/wily/pcscd) and try again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1511674 Title: Memory leak Status in pcsc-lite package in Ubuntu: New Bug description: I noticed that pcscd consumes a lot of memory (5GB after 48h since start) in one of my computers (ubuntu 14.04 64-bit pcsc-lite version 1.8.10.) In debug mode pcscd shows a lot of USB "device removed" notifications: 0102 hotplug_libudev.c:594:HPEstablishUSBNotifications() Device removed 1297 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 [cut - long list of usb devices] 0246 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x03EB, PID: 0x2044, path: /dev/bus/usb/001/067 00022327 winscard_svc.c:319:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 00500329 winscard_svc.c:319:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 00500341 winscard_svc.c:319:ContextThread() Received command: CMD_GET_READERS_STATE from client 5 Flood of "device removed" messages was caused by some broken USB device (not card reader - CDC-ACM device), but it doesn't explain why pcscd allocated 5GB of memory. Is it some memory leak in pcscd? lsb_release -rd: Description: Ubuntu 14.04.3 LTS Release: 14.04 pcscd: Installed: 1.8.10-1ubuntu1 Candidate: 1.8.10-1ubuntu1 Version table: *** 1.8.10-1ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1511674/+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 1512473] [NEW] Some cross-references are broken, while editing the document, or Updating All Fields
Public bug reported:
I am using Libre Office Version: 5.0.2-0ubuntu1 in Xubuntu 15.10, and
some my cross-references started to broke ('Error: Reference source not
found') while editing the document, or Updating All Fields. This was not
happening while I was in Xubuntu 15.04, so I suspect it is related to
the update from 4.4.2 to 5.0.2. Also, 4.4.5 version, installed in
parallel with 5.0.2 from the debs from libreoffice.org website, also
does not work.
I will try to install in parallel 4.4.2, to see if it works for me.
Thank you very much for your help.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libreoffice 1:5.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Nov 2 16:44:41 2015
InstallationDate: Installed on 2014-10-25 (373 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages wily
--
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/1512473
Title:
Some cross-references are broken, while editing the document, or
Updating All Fields
Status in libreoffice package in Ubuntu:
New
Bug description:
I am using Libre Office Version: 5.0.2-0ubuntu1 in Xubuntu 15.10, and
some my cross-references started to broke ('Error: Reference source
not found') while editing the document, or Updating All Fields. This
was not happening while I was in Xubuntu 15.04, so I suspect it is
related to the update from 4.4.2 to 5.0.2. Also, 4.4.5 version,
installed in parallel with 5.0.2 from the debs from libreoffice.org
website, also does not work.
I will try to install in parallel 4.4.2, to see if it works for me.
Thank you very much for your help.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libreoffice 1:5.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Nov 2 16:44:41 2015
InstallationDate: Installed on 2014-10-25 (373 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.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/1512473/+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 1506490] Re: Print dialog - getting printer information failed
Assuming that this is the same bug in gtk, I'm leaving this open to SRU the fix to gtk 3.10.8 on Trusty. The other bug is for gtk 3.14 and probably contains changes that wouldn't be good for Trusty. ** This bug is no longer a duplicate of bug 1473006 [SRU] New upstream release 3.14.15 ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Medium ** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1506490 Title: Print dialog - getting printer information failed Status in ubuntu-mate: New Status in gtk+3.0 package in Ubuntu: New Bug description: Running Ubuntu Mate 14.04 a number of printers fail when used from the print dialog. However they can be printed to successfully from LIbreOffice and can also have a test page sent to them. When using the system print dialog the status of the printer is set to: 'Getting printer information failed' And the Print button is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1506490/+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 1512467] [NEW] Release no-change rebuild for ocaml transition
Public bug reported: The havea package needs to be no-change rebuilt for the ocaml transition. See attached debdiff for details. Thank you! ** Affects: hevea (Ubuntu) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: In Progress ** Patch added: "No-change rebuild debdiff" https://bugs.launchpad.net/bugs/1512467/+attachment/4511469/+files/hevea_2.23-2build1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hevea in Ubuntu. https://bugs.launchpad.net/bugs/1512467 Title: Release no-change rebuild for ocaml transition Status in hevea package in Ubuntu: In Progress Bug description: The havea package needs to be no-change rebuilt for the ocaml transition. See attached debdiff for details. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hevea/+bug/1512467/+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 1512454] [NEW] Refresh change colours
Public bug reported: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal image) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Zrzut ekranu z 2015-10-22 22_26_07.png" https://bugs.launchpad.net/bugs/1512454/+attachment/4511460/+files/Zrzut%20ekranu%20z%202015-10-22%2022_26_07.png -- 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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: New Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1512454/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
after upgrading from 15.04 to 15.10 I get the same error when I connect my iPhone (5s) to any usb-port of my x220. only the iphone is causing this and the iphone is "locked" (does not connect to anything via usb). worked fine under 15.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() Status in upower package in Ubuntu: Fix Released Bug description: it looks like nothing happend. When I switch on the PC and after loging in this window with 'report an error/bug' appeard. so I guess it is minor. thanks for doing :) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 Date: Wed Apr 9 15:37:43 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-04-04 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 (20140326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0xb74e9919 : mov (%esi),%eax PC (0xb74e9919) ok source "(%esi)" (0x302e) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: upower StacktraceTop: service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 property_list_service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 ?? () g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: upowerd crashed with SIGSEGV in service_client_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1512454] Re: Refresh change colours
I also add another screen shot here ** Attachment added: "Zrzut ekranu z 2015-11-02 18_33_04.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1512454/+attachment/4511466/+files/Zrzut%20ekranu%20z%202015-11-02%2018_33_04.png -- 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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: New Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1512454/+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 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
unity-greeter has code to kill upstart, but for some reason this isn't being executed. My best guess is that unity-greeter often (if not always) dies before it exits the GTK main loop. Does it receive a second SIGTERM, or a SIGPIPE? (When lightdm says "Stopping display server, no sessions require it", I would think.) This should be testable. Amending my earlier comment #7, I do see "Got a SIGTERM" some of the time, but I hardly ever see "Cleaning up" (when unlocking; new logins are another story). Indeed upstart is not to blame: it shuts itself off cleanly when signalled; the problem seems to be that unity-greeter doesn't send out that signal as it is supposed to. -- 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/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed Status in Light Display Manager: New Status in lightdm package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: dm-tool lock starts a new lightdm greeter (for unlocking) and a new logind session. After unlocking the greeter disappears, but the logind session never closes. loginctl session status c24 reports something like: c24 - lightdm (103) Since: Thu 2014-05-22 18:38:27 CEST; 30min ago Leader: 7872 Seat: seat0; vc8 Display: :1 Service: lightdm-greeter; type x11; class greeter State: closing CGroup: systemd:/user/103.user/c24.session └─7907 init --user --startup-event indicator-services-start This results in an accumulation of stale lightdm sessions after using e.g. a session locker for a while. I get this issue on a freshly installed and fully updated Xubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+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 1505328] Re: Cups SSL is vulernable to POODLE
** Patch added: "now current debdiff (fixes accidentally included file)" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1505328/+attachment/4511465/+files/cups_1.7.2-0ubuntu1.7.debdiff ** Patch removed: "debdiff for 14.04" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1505328/+attachment/4511335/+files/cups_1.7.2-0ubuntu1.7.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1505328 Title: Cups SSL is vulernable to POODLE Status in cups package in Ubuntu: New Bug description: On 12.04 and 14.04 if you enable cups ssl you are vulnerable to poodle, and there does not appear to be any way to mitigate it in Cups config. Ubuntu 14.04 - https://www.ssllabs.com/ssltest/analyze.html?d=190.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on Ubuntu 12.04 - https://www.ssllabs.com/ssltest/analyze.html?d=191.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on Fixed in wily - https://www.ssllabs.com/ssltest/analyze.html?d=192.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on Upstream fix - https://www.cups.org/str.php?L4476 Should we disable ssvl3 in the 12.04/14.04 cups by default and backport the option to turn it back on? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1505328/+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 1492655] Re: upower crashed after plugging usb device
*** This bug is a duplicate of bug 1305699 *** https://bugs.launchpad.net/bugs/1305699 it's only the iphone that is causing this problem and I have to mention that my iphone is configured to block usb devices (my employers phone) so I can't access it neither on windows nor on windows via usb... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1492655 Title: upower crashed after plugging usb device Status in upower package in Ubuntu: Confirmed Bug description: I plugged in my iphone into my usb port and got no connection, then I plugged it into another usb port and upower crashed. below is the dmesg log. [ 249.000800] traps: upowerd[1710] general protection ip:7ffac40f31cb sp:7ffdad8ebeb0 error:0 in libc-2.21.so[7ffac4074000+1c] [ 250.830414] panel-5-power-m[1753]: segfault at 8 ip 7fe58fe5c6fa sp 7ffc40ce3778 error 4 in libc-2.21.so[7fe58fdd1000+1c] [ 255.001463] traps: upowerd[2037] general protection ip:7f11da00f693 sp:7ffc517d43d0 error:0 in libplist.so.3.0.0[7f11da009000+a000] [ 255.764318] panel-5-power-m[2040]: segfault at 8 ip 7ff6e0cf76fa sp 7ffdf90df9d8 error 4 in libc-2.21.so[7ff6e0c6c000+1c] [ 258.000892] traps: upowerd[2086] general protection ip:7fd25097c1cb sp:7ffe045442e0 error:0 in libc-2.21.so[7fd2508fd000+1c] [ 263.782267] panel-5-power-m[2205]: segfault at 8 ip 7f3086c2f6fa sp 7ffd43f574e8 error 4 in libc-2.21.so[7f3086ba4000+1c] [ 266.002118] traps: upowerd[2211] general protection ip:7f23d0f3f1cb sp:7ffc1b4a2b10 error:0 in libc-2.21.so[7f23d0ec+1c] [ 273.784371] panel-5-power-m[2357]: segfault at 8 ip 7fa697e5a6fa sp 7fff80fb5d98 error 4 in libc-2.21.so[7fa697dcf000+1c] [ 276.001565] traps: upowerd[2363] general protection ip:7f1591a971cb sp:7ffcd9dbdb60 error:0 in libc-2.21.so[7f1591a18000+1c] [ 276.827205] panel-5-power-m[2401]: segfault at 8 ip 7fc32e4f76fa sp 7ffea2e4cc38 error 4 in libc-2.21.so[7fc32e46c000+1c] [ 279.848223] panel-5-power-m[2453]: segfault at 8 ip 7f67caf2a6fa sp 7ffe2cca8958 error 4 in libc-2.21.so[7f67cae9f000+1c] [ 284.001686] traps: upowerd[2501] general protection ip:7fd7125011cb sp:7ffe31685b20 error:0 in libc-2.21.so[7fd712482000+1c] [ 287.001308] traps: upowerd[2538] general protection ip:7fa08e0641cb sp:7ffe1acc0ab0 error:0 in libc-2.21.so[7fa08dfe5000+1c] [ 290.000986] traps: upowerd[2620] general protection ip:7f283691b1cb sp:7ffc7833ed70 error:0 in libc-2.21.so[7f283689c000+1c] [ 293.000365] traps: upowerd[2742] general protection ip:7f9610bb91cb sp:7fffd83804c0 error:0 in libc-2.21.so[7f9610b3a000+1c] [ 296.001657] traps: upowerd[2874] general protection ip:7f4c8ca461cb sp:7ffed229c480 error:0 in libc-2.21.so[7f4c8c9c7000+1c] [ 305.001335] traps: upowerd[3308] general protection ip:7f92dd6da1cb sp:7ffe62057490 error:0 in libc-2.21.so[7f92dd65b000+1c] [ 308.001320] traps: upowerd[3384] general protection ip:7fea523a81cb sp:7fff3de785a0 error:0 in libc-2.21.so[7fea52329000+1c] [ 314.001036] traps: upowerd[3475] general protection ip:7fc37c7a61cb sp:7ffda5f5e630 error:0 in libc-2.21.so[7fc37c727000+1c] [ 317.001537] traps: upowerd[3519] general protection ip:7f8da1f911cb sp:7ffdc042c440 error:0 in libc-2.21.so[7f8da1f12000+1c] [ 325.390590] traps: upowerd[3556] general protection ip:7fd75cbb01cb sp:7ffddf371cb0 error:0 in libc-2.21.so[7fd75cb31000+1c] [ 328.000949] traps: upowerd[3886] general protection ip:7f77012161cb sp:7fff096428f0 error:0 in libc-2.21.so[7f7701197000+1c] [ 333.001386] traps: upowerd[4042] general protection ip:7f12bc7351cb sp:7ffea69256e0 error:0 in libc-2.21.so[7f12bc6b6000+1c] [ 336.000552] traps: upowerd[4087] general protection ip:7fa0a39131cb sp:7ffd7c666d50 error:0 in libc-2.21.so[7fa0a3894000+1c] [ 339.001602] traps: upowerd[4209] general protection ip:7f744fd241cb sp:7ffe3d033260 error:0 in libc-2.21.so[7f744fca5000+1c] [ 342.001113] upowerd[4390]: segfault at 0 ip 7faa9e668a1f sp 7ffeec04c190 error 4 in libplist.so.3.0.0[7faa9e661000+a000] [ 345.001387] traps: upowerd[4567] general protection ip:7f75ba9de1cb sp:7ffe69a21c00 error:0 in libc-2.21.so[7f75ba95f000+1c] [ 350.001263] traps: upowerd[4642] general protection ip:7fb7050d01cb sp:7ffec44a7740 error:0 in libc-2.21.so[7fb705051000+1c] [ 353.001649] traps: upowerd[4678] general protection ip:7fdceaa911cb sp:7ffcf03ce3b0 error:0 in libc-2.21.so[7fdceaa12000+1c] [ 356.001052] traps: upowerd[4714] general protection ip:7f143c2a31cb sp:7ffc7c58d6f0 error:0 in libc-2.21.so[7f143c224000+1c] [ 359.001678] traps: upowerd[4750] general protection ip:7f27b35371cb sp:7ffc4ed225f0 error:0 in libc-2.21.so[7f27b34b8000+1c] [ 362.001725] traps: upowerd[4798] gen
[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5
Tested the proposed driver, working fine for me. Ubuntu 15.10, Unity, Radeon HD 7800 -- 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/1493888 Title: FGLRX incompatible with gcc 5 Status in Release Notes for Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer source package in Wily: Fix Committed Bug description: SRU Request: [Impact] The fglrx driver is not compatible with gcc 5.x. This causes the kernel module to crash on initialisation. As a result, users will boot into a black screen, as X will fail (except on Intel+AMD hybrid systems, where intel is used). [Test Case] 1. Either install (or upgrade to) Ubuntu 15.10 and fglrx 2. Reboot 3. Check the display, and the output of the "dmesg | grep fglrx" command (to see the actual crash) Expected results: the system should be able to start X correctly. Actual results: The kernel module fails and X doesn't start. [Regression Potential] Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be replaced with the proper fix once AMD makes it available. __ With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am able to SSH into the machine. I booted the older kernel (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and using xserver-xorg-video-radeon I am able to get the graphics working, but even it has issues with my display port (The DVI ports are working correctly). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 09:29:54 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2011-01-07 (1705 days ago) InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fglrx-installer UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+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 1420395] Re: [mako] upower consuming over 17% cpu when in idle
not seen in some time ** Tags removed: battery ** Tags added: power-bugs ** Changed in: canonical-devices-system-image Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1420395 Title: [mako] upower consuming over 17% cpu when in idle Status in Canonical System Image: Incomplete Status in upower package in Ubuntu: Confirmed Bug description: From the meta battery bug # 1372413 mako running 191 As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool mpdecision and systemd-udevd also change their behavior. The upower cpu consumption is just a side effect of the amount of battery related events the kernel send, and specific to mako. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+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 1492655] Re: upower crashed after plugging usb device
*** This bug is a duplicate of bug 1305699 *** https://bugs.launchpad.net/bugs/1305699 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1492655 Title: upower crashed after plugging usb device Status in upower package in Ubuntu: Confirmed Bug description: I plugged in my iphone into my usb port and got no connection, then I plugged it into another usb port and upower crashed. below is the dmesg log. [ 249.000800] traps: upowerd[1710] general protection ip:7ffac40f31cb sp:7ffdad8ebeb0 error:0 in libc-2.21.so[7ffac4074000+1c] [ 250.830414] panel-5-power-m[1753]: segfault at 8 ip 7fe58fe5c6fa sp 7ffc40ce3778 error 4 in libc-2.21.so[7fe58fdd1000+1c] [ 255.001463] traps: upowerd[2037] general protection ip:7f11da00f693 sp:7ffc517d43d0 error:0 in libplist.so.3.0.0[7f11da009000+a000] [ 255.764318] panel-5-power-m[2040]: segfault at 8 ip 7ff6e0cf76fa sp 7ffdf90df9d8 error 4 in libc-2.21.so[7ff6e0c6c000+1c] [ 258.000892] traps: upowerd[2086] general protection ip:7fd25097c1cb sp:7ffe045442e0 error:0 in libc-2.21.so[7fd2508fd000+1c] [ 263.782267] panel-5-power-m[2205]: segfault at 8 ip 7f3086c2f6fa sp 7ffd43f574e8 error 4 in libc-2.21.so[7f3086ba4000+1c] [ 266.002118] traps: upowerd[2211] general protection ip:7f23d0f3f1cb sp:7ffc1b4a2b10 error:0 in libc-2.21.so[7f23d0ec+1c] [ 273.784371] panel-5-power-m[2357]: segfault at 8 ip 7fa697e5a6fa sp 7fff80fb5d98 error 4 in libc-2.21.so[7fa697dcf000+1c] [ 276.001565] traps: upowerd[2363] general protection ip:7f1591a971cb sp:7ffcd9dbdb60 error:0 in libc-2.21.so[7f1591a18000+1c] [ 276.827205] panel-5-power-m[2401]: segfault at 8 ip 7fc32e4f76fa sp 7ffea2e4cc38 error 4 in libc-2.21.so[7fc32e46c000+1c] [ 279.848223] panel-5-power-m[2453]: segfault at 8 ip 7f67caf2a6fa sp 7ffe2cca8958 error 4 in libc-2.21.so[7f67cae9f000+1c] [ 284.001686] traps: upowerd[2501] general protection ip:7fd7125011cb sp:7ffe31685b20 error:0 in libc-2.21.so[7fd712482000+1c] [ 287.001308] traps: upowerd[2538] general protection ip:7fa08e0641cb sp:7ffe1acc0ab0 error:0 in libc-2.21.so[7fa08dfe5000+1c] [ 290.000986] traps: upowerd[2620] general protection ip:7f283691b1cb sp:7ffc7833ed70 error:0 in libc-2.21.so[7f283689c000+1c] [ 293.000365] traps: upowerd[2742] general protection ip:7f9610bb91cb sp:7fffd83804c0 error:0 in libc-2.21.so[7f9610b3a000+1c] [ 296.001657] traps: upowerd[2874] general protection ip:7f4c8ca461cb sp:7ffed229c480 error:0 in libc-2.21.so[7f4c8c9c7000+1c] [ 305.001335] traps: upowerd[3308] general protection ip:7f92dd6da1cb sp:7ffe62057490 error:0 in libc-2.21.so[7f92dd65b000+1c] [ 308.001320] traps: upowerd[3384] general protection ip:7fea523a81cb sp:7fff3de785a0 error:0 in libc-2.21.so[7fea52329000+1c] [ 314.001036] traps: upowerd[3475] general protection ip:7fc37c7a61cb sp:7ffda5f5e630 error:0 in libc-2.21.so[7fc37c727000+1c] [ 317.001537] traps: upowerd[3519] general protection ip:7f8da1f911cb sp:7ffdc042c440 error:0 in libc-2.21.so[7f8da1f12000+1c] [ 325.390590] traps: upowerd[3556] general protection ip:7fd75cbb01cb sp:7ffddf371cb0 error:0 in libc-2.21.so[7fd75cb31000+1c] [ 328.000949] traps: upowerd[3886] general protection ip:7f77012161cb sp:7fff096428f0 error:0 in libc-2.21.so[7f7701197000+1c] [ 333.001386] traps: upowerd[4042] general protection ip:7f12bc7351cb sp:7ffea69256e0 error:0 in libc-2.21.so[7f12bc6b6000+1c] [ 336.000552] traps: upowerd[4087] general protection ip:7fa0a39131cb sp:7ffd7c666d50 error:0 in libc-2.21.so[7fa0a3894000+1c] [ 339.001602] traps: upowerd[4209] general protection ip:7f744fd241cb sp:7ffe3d033260 error:0 in libc-2.21.so[7f744fca5000+1c] [ 342.001113] upowerd[4390]: segfault at 0 ip 7faa9e668a1f sp 7ffeec04c190 error 4 in libplist.so.3.0.0[7faa9e661000+a000] [ 345.001387] traps: upowerd[4567] general protection ip:7f75ba9de1cb sp:7ffe69a21c00 error:0 in libc-2.21.so[7f75ba95f000+1c] [ 350.001263] traps: upowerd[4642] general protection ip:7fb7050d01cb sp:7ffec44a7740 error:0 in libc-2.21.so[7fb705051000+1c] [ 353.001649] traps: upowerd[4678] general protection ip:7fdceaa911cb sp:7ffcf03ce3b0 error:0 in libc-2.21.so[7fdceaa12000+1c] [ 356.001052] traps: upowerd[4714] general protection ip:7f143c2a31cb sp:7ffc7c58d6f0 error:0 in libc-2.21.so[7f143c224000+1c] [ 359.001678] traps: upowerd[4750] general protection ip:7f27b35371cb sp:7ffc4ed225f0 error:0 in libc-2.21.so[7f27b34b8000+1c] [ 362.001725] traps: upowerd[4798] general protection ip:7fe75e24c1cb sp:7ffc21fd27a0 error:0 in libc-2.21.so[7f
