[Desktop-packages] [Bug 1439026] [NEW] /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding shotwell. This problem was most recently seen with version 0.20.2-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/faf6570a403688de1785ba9583b641e052e0bbe4 contains more details. ** Affects: shotwell (Ubuntu) Importance: High Status: Confirmed ** Tags: vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1439026 Title: /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit Status in shotwell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding shotwell. This problem was most recently seen with version 0.20.2-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/faf6570a403688de1785ba9583b641e052e0bbe4 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1439026/+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 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
Reverting job (jeppekdahl)'s changes ** Changed in: libdrm (Ubuntu Trusty) Assignee: job (jeppekdahl) = (unassigned) ** Changed in: x11proto-fonts (Ubuntu Trusty) Assignee: job (jeppekdahl) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1400626 Title: Please backport xtrans, libdrm, x11proto-{fonts,core} packages for 14.04.2 Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-snapshot package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in x11proto-fonts package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xtrans package in Ubuntu: Invalid Status in libdrm source package in Trusty: Fix Released Status in llvm-toolchain-snapshot source package in Trusty: Fix Released Status in x11proto-core source package in Trusty: Fix Released Status in x11proto-fonts source package in Trusty: Fix Released Status in xorg source package in Trusty: Fix Released Status in xtrans source package in Trusty: Fix Released Bug description: In order to upload the new xorg-server we need to backport the following packages from utopic: libdrm x11proto-core x11proto-fonts xtrans libdrm 2.4.52-1-2.4.56-1 seems to have the following changes: - Hides private symbols from all libdrm libraries - fixes MSAA on Hawaii (radeon). - Adds cherryview pci-ids (intel). - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd. - Fixes to exynos and freedreno. - Enables building libdrm-freedreno1 and libdrm-exynos1 x11proto-core's main change appears to be changing from the 'pointer' type to 'void *': https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz x11proto-fonts' main change is the same as x11proto-core, but the documentation is reformatted too: https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz xtrans seems to have 2 minor changes, increase default unix pipe size and add support for systemd socket activation: https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz xorg needs to be slightly updated, to allow xserver-xorg to provide the unrenamed lts-utopic, and to allow xorg to be installed with the renamed xorg-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+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 1415958] Re: Laptop + external display does not suspend on lid close
I meant that when you dock or undock a laptop you get a particular evdev event (SW_DOCK), which logind checks for. This tells apart the simple external monitor case from laptop sits closed in dock and only uses external monitor. That the laptop doesn't suspend under a VT is not expected (unless you changed HandleLidSwitch=). That might warrant another bug report against systemd. But under unity it's definitively unity-settings-daemon's policy which gets applied here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1415958 Title: Laptop + external display does not suspend on lid close Status in unity-settings-daemon package in Ubuntu: New Bug description: Since update to Vivid, laptop does not suspend on lid close if an external monitor is connected, even though suspend is selected in the power settings for lid close. The display flashes and apps move to external display. Syslog shows no attempt to suspend. On Utopic it suspended ok with external monitor. In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are messages in syslog at that time but I suspect they may be a different issue: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment WORKAROUND: Suspend via the menu. WORKAROUND: Disconnect external monitor first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 29 15:04:52 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:17a9] InstallationDate: Installed on 2014-12-27 (33 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 29 15:00:08 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13890 vendor SEC xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1415958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
The last working versions for me were xserver-xorg- core_1.16.2.901-1ubuntu4 and xserver-xorg-video-radeon_7.5.0-1ubuntu1 1.17 introduced the problem. -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us. Thanks in advance. Cheers, Christian To manage notifications about this bug go to:
[Desktop-packages] [Bug 1438740] Re: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply()
I need to boot from this live-cd and there install steam and the game to test it, is that correct? I have another 14.04 ubuntu where the bug does not happen with the same game, so it might be hardware-specific. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1438740 Title: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply() Status in gnome-panel package in Ubuntu: Incomplete Bug description: The game where I observe this is Magicite, however it seems to be the case for other steam games as well. I run gnome-flashback session with compiz on Ubuntu 14.04. When the game starts, the panel crashes and disappears. I have to restart it manually in a shell (it does not automatically respawn). ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu12.2 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 31 17:44:27 2015 ExecutablePath: /usr/bin/gnome-panel ExecutableTimestamp: 1412098123 GsettingsChanges: InstallationDate: Installed on 2014-09-05 (207 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: gnome-panel ProcCwd: /home/ps Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip fuse lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1438740/+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 1438806] Re: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1438806 Title: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in emacs24 package in Ubuntu: New Bug description: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: emacs24 24.3+1-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 Date: Tue Mar 31 12:15:16 2015 DuplicateSignature: package:emacs24:24.3+1-2ubuntu1:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-03-31 (0 days ago) InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: emacs24 Title: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to trusty on 2015-03-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1438806/+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 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c Status in central project for keyboard configuration: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: New Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: When typing in a US-international keyboard with dead-keys (or UK-international), typing 'c results in an accented c instead of a cedilla. There is a workaround, which is editing the /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules file and changing the line cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa to cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en (add the 'en' at the end). However, every time some update on this file is applied, one looses the change, and we get back to the accented c. That means having to modify the file again, logout and login. For me this is no problem. But for my brother, mom, dad, etc, it is always something that at least makes me less proud of having convinced them to use Ubuntu, because they don't know what to do each time this happens. I think we really need a configurable keyboard layout, or at least (and that would be very easy), the inclusion of alternate layouts on install that for the dead-key options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla. This change is relevant for at least Portuguese and French. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)
thanks for the info (and your work, all) to fix this issue and provide workarounds in the meantime. Ubuntu LTS and the ecosystem around it (launchpad, repos, community, etc) rock! :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1251281 Title: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting) Status in The GNOME 2 Session Manager: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-session source package in Trusty: Fix Committed Status in gnome-session source package in Utopic: Fix Committed Status in gnome-flashback source package in Vivid: Fix Released Status in gnome-session source package in Vivid: Fix Released Status in gnome-session package in Debian: New Bug description: == Impact == It was impossible to launch a gnome-session-based desktop on a system where hardware accelerations is not available (such as old hardware, or when using a remote desktop). That looks like a quite popular use case — more than a hundred of people marked this bug as affecting them. == Test Case == The original bug description below contains a test case. == Proposed Fix == The fix backports an upstream commit which adds --disable-acceleration-check commandline option, and makes Upstart user session pass that flag to gnome-session when the session is gnome-fallback (aka gnome-flashback-metacity). Of course, that option can be used with other sessions as well. This was fixed in vivid in version 3.14.0-2ubuntu4. == Regression Potential == The option was accepted upstream, and nobody complained so far. So the regression potential should be low. This bug will cause static grey or black screen instead of opening remote session using Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting from x2goclient, rdpclient(reminna/vinagre/mstsc), SSH, VNC, NOMACHINE and etc. == Original Description == 1) lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 2) apt-cache policy gnome-session gnome-session: Installed: 3.9.90-0ubuntu12 Candidate: 3.9.90-0ubuntu12 Version table: *** 3.9.90-0ubuntu12 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen is when one installs xrdp on the host and attempts to use remmina or vinagre on a Ubuntu 14.04 client to RDP in, it works. 4) What happens instead is it shows a gray static screen as per attached screenshot. This would appear an issue with gnome-session as per client log: cat .xsession-errors.old Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. init: indicator-application main process ended, respawning init: indicator-application main process ended, respawning init: indicator-application respawning too fast, stopped Xsession: X session started for at Sun Jul 20 15:25:59 CDT 2014 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 localuser:moniker being added to access control list X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 109 (X_ChangeHosts) Value in failed request: 0x5 Serial number of failed request: 6 Current serial number in output stream: 8 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 gnome-session-is-accelerated: No composite extension. gnome-session-check-accelerated: Helper exited with code 256 ** (process:2565): WARNING **: software acceleration check failed: Child process exited with code 1 ** (x-session-manager:2565): CRITICAL **: We failed, but the fail whale is dead. Sorry The following is not a WORKAROUND, create /etc/xorg.conf : Section Device Identifier Intel Graphics Driver Intel Option DRI False EndSection ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session 3.9.90-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 15:35:23 2014 InstallationDate: Installed on 2014-06-22 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty
[Desktop-packages] [Bug 1439026] Re: /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit
** Changed in: shotwell (Ubuntu) Status: Confirmed = Triaged ** Bug watch added: GNOME Bug Tracker #747159 https://bugzilla.gnome.org/show_bug.cgi?id=747159 ** Also affects: shotwell via https://bugzilla.gnome.org/show_bug.cgi?id=747159 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1439026 Title: /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit Status in Shotwell: Unknown Status in shotwell package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding shotwell. This problem was most recently seen with version 0.20.2-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/faf6570a403688de1785ba9583b641e052e0bbe4 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1439026/+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 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Also affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. Status in Déjà Dup Backup Tool: New Status in Duplicity - Bandwidth Efficient Encrypted Backup: New Status in deja-dup package in Ubuntu: New Bug description: For 4 days déjà dup hasn't been able to perform a backup. It fails with the error Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (type 'exceptions.IOError', IOError('CRC check failed 0x8434f7d2L != 0x3d503338L',), traceback object at 0x9fe0554) There is another similar bug #676767 where deleting ~/.cache/deja-dup helps. In this case it doesn't. I'm quite certain that my backup drive isn't corrupted. (It's a raid5.) I'd be happy to provide any additional information needed. -- System information: Ubuntu 11.10 deja-dup 20.0-0ubuntu3 duplicity 0.6.15-0ubuntu2 Logs: deja-dup.log: http://pastie.org/2705320 deja-dup.gsettings: http://pastie.org/2705322 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+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 1438806] Re: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
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 emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1438806 Title: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in emacs24 package in Ubuntu: New Bug description: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: emacs24 24.3+1-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 Date: Tue Mar 31 12:15:16 2015 DuplicateSignature: package:emacs24:24.3+1-2ubuntu1:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-03-31 (0 days ago) InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) SourcePackage: emacs24 Title: package emacs24 24.3+1-2ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to trusty on 2015-03-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1438806/+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 1439006] Re: [FFe] Install Fcitx for Japanese users
What makes you think this is the right thing to do so close to the release? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1439006 Title: [FFe] Install Fcitx for Japanese users Status in im-config package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: According to my proposal [1], Fcitx should be default for Japanese uses on Vivid release cycle. https://lists.ubuntu.com/archives/ubuntu-desktop/2015-March/004645.html Ref: https://bugs.launchpad.net/ubuntu/+source/language- selector/+bug/1430893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1439006/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Assignee: Toluwalope (tolentee) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: Confirmed Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is solved - see https://askubuntu.com/questions/576523 for details. **If you want to comment:** Please consider if you have something meaningful to contribute to the 2500+ people who will get an email. **If you are an Ubuntu developer:** thanks for looking into this! :D Nvidia kernel module failed to build on kernel 3.13.0-2 Yesterday when the new kernel was pushed, the dkms process failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 3.13.0-2-generic Date: Sun Jan 12 01:28:35 2014 InstallationDate: Installed on 2013-11-03 (69 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageVersion: 331.20-0ubuntu9 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430358] Re: lubuntu crash on start
** Summary changed: - ubuntu crash on start + lubuntu crash on start -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1430358 Title: lubuntu crash on start Status in xorg-server package in Ubuntu: New Bug description: lubuntu start with black screen. Now I can't log in to Lubuntu enviroment. When i try to log in massage is showede: Starting version 219 [ OK ] Started Light Display Manager. and the loging screen si showed again. In past booting up is slow but i was able to log in. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432681 ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: xserver-xorg-core 2:1.16.2.901-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu2 Architecture: i386 Date: Tue Mar 10 12:41:44 2015 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-03-16 (724 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server UpgradeStatus: Upgraded to vivid on 2015-02-27 (10 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1430358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1439014] [NEW] pidgin crashed with SIGSEGV in call_init()
Public bug reported: Pidgin crashed on launch when startet from menu. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Apr 1 07:51:44 2015 Disassembly: = 0x5:Cannot access memory at address 0x5 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2013-03-16 (745 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: pidgin SegvAnalysis: Segfault happened at: 0x5: Cannot access memory at address 0x5 PC (0x0005) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: ?? () ?? () from /usr/lib/pidgin/libpurpletorchat.so ?? () from /usr/lib/pidgin/libpurpletorchat.so call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 Title: pidgin crashed with SIGSEGV in call_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace third-party-packages vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1439014 Title: pidgin crashed with SIGSEGV in call_init() Status in pidgin package in Ubuntu: New Bug description: Pidgin crashed on launch when startet from menu. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Apr 1 07:51:44 2015 Disassembly: = 0x5: Cannot access memory at address 0x5 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2013-03-16 (745 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: pidgin SegvAnalysis: Segfault happened at: 0x5: Cannot access memory at address 0x5 PC (0x0005) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: ?? () ?? () from /usr/lib/pidgin/libpurpletorchat.so ?? () from /usr/lib/pidgin/libpurpletorchat.so call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 Title: pidgin crashed with SIGSEGV in call_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1439014/+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 1439014] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1439014/+attachment/4362660/+files/ThreadStacktrace.txt ** Changed in: pidgin (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1439014 Title: pidgin crashed with SIGSEGV in call_init() Status in pidgin package in Ubuntu: Invalid Bug description: Pidgin crashed on launch when startet from menu. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Apr 1 07:51:44 2015 Disassembly: = 0x5: Cannot access memory at address 0x5 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2013-03-16 (745 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: pidgin SegvAnalysis: Segfault happened at: 0x5: Cannot access memory at address 0x5 PC (0x0005) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: ?? () ?? () from /usr/lib/pidgin/libpurpletorchat.so ?? () from /usr/lib/pidgin/libpurpletorchat.so call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 Title: pidgin crashed with SIGSEGV in call_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1439014/+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 1439014] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1439014/+attachment/4362658/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1439014 Title: pidgin crashed with SIGSEGV in call_init() Status in pidgin package in Ubuntu: Invalid Bug description: Pidgin crashed on launch when startet from menu. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Apr 1 07:51:44 2015 Disassembly: = 0x5: Cannot access memory at address 0x5 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2013-03-16 (745 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: pidgin SegvAnalysis: Segfault happened at: 0x5: Cannot access memory at address 0x5 PC (0x0005) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: ?? () ?? () from /usr/lib/pidgin/libpurpletorchat.so ?? () from /usr/lib/pidgin/libpurpletorchat.so call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 Title: pidgin crashed with SIGSEGV in call_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1439014/+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 1439014] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for gcc-5-base no debug symbol package found for dmsetup no debug symbol package found for libisc-export95 no debug symbol package found for gconf-service no debug symbol package found for multiarch-support no debug symbol package found for libflac8 no debug symbol package found for libdevmapper1.02.1 no debug symbol package found for libirs-export91 no debug symbol package found for libperl5.20 no debug symbol package found for perl-base no debug symbol package found for xdg-user-dirs no debug symbol package found for libgtkspell0 no debug symbol package found for debianutils no debug symbol package found for libisccfg-export90 no debug symbol package found for libdns-export100 no debug symbol package found for sed no debug symbol package found for libtag1c2a ca-certificates version 20141019ubuntu0.14.10.1 required, but 20141019 is available no debug symbol package found for iproute2 no debug symbol package found for libgtkspell0 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1439014/+attachment/4362648/+files/CoreDump.gz ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1439014 Title: pidgin crashed with SIGSEGV in call_init() Status in pidgin package in Ubuntu: Invalid Bug description: Pidgin crashed on launch when startet from menu. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Apr 1 07:51:44 2015 Disassembly: = 0x5: Cannot access memory at address 0x5 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2013-03-16 (745 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: pidgin SegvAnalysis: Segfault happened at: 0x5: Cannot access memory at address 0x5 PC (0x0005) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: ?? () ?? () from /usr/lib/pidgin/libpurpletorchat.so ?? () from /usr/lib/pidgin/libpurpletorchat.so call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 Title: pidgin crashed with SIGSEGV in call_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1439014/+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 1439014]
StacktraceTop: ?? () ?? () ?? () call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1439014 Title: pidgin crashed with SIGSEGV in call_init() Status in pidgin package in Ubuntu: Invalid Bug description: Pidgin crashed on launch when startet from menu. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Apr 1 07:51:44 2015 Disassembly: = 0x5: Cannot access memory at address 0x5 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2013-03-16 (745 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: pidgin SegvAnalysis: Segfault happened at: 0x5: Cannot access memory at address 0x5 PC (0x0005) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: ?? () ?? () from /usr/lib/pidgin/libpurpletorchat.so ?? () from /usr/lib/pidgin/libpurpletorchat.so call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 Title: pidgin crashed with SIGSEGV in call_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1439014/+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 1439014] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1439014/+attachment/4362659/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1439014 Title: pidgin crashed with SIGSEGV in call_init() Status in pidgin package in Ubuntu: Invalid Bug description: Pidgin crashed on launch when startet from menu. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pidgin 1:2.10.9-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: LXDE Date: Wed Apr 1 07:51:44 2015 Disassembly: = 0x5: Cannot access memory at address 0x5 ExecutablePath: /usr/bin/pidgin InstallationDate: Installed on 2013-03-16 (745 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1) ProcCmdline: pidgin SegvAnalysis: Segfault happened at: 0x5: Cannot access memory at address 0x5 PC (0x0005) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: pidgin StacktraceTop: ?? () ?? () from /usr/lib/pidgin/libpurpletorchat.so ?? () from /usr/lib/pidgin/libpurpletorchat.so call_init (l=0xb7dd6bf8, argc=8388608, argc@entry=1, argv=0xbf9a2884, env=0xbf9a288c) at dl-init.c:58 call_init (env=0xbf9a288c, argv=0xbf9a2884, argc=1, l=optimized out) at dl-init.c:30 Title: pidgin crashed with SIGSEGV in call_init() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1439014/+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 1436072] Re: shotwell crashed with SIGSEGV in g_signal_emit_valist()
*** This bug is a duplicate of bug 1439026 *** https://bugs.launchpad.net/bugs/1439026 ** This bug is no longer a duplicate of bug 1431121 shotwell crashed with SIGSEGV in gtk_application_impl_handle_window_realize() ** This bug has been marked a duplicate of bug 1439026 /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1436072 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() Status in shotwell package in Ubuntu: New Bug description: This happened after cropping an image. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: shotwell 0.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Mar 24 22:05:55 2015 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2014-02-13 (403 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) ProcCmdline: shotwell /home/username/Dropbox/Public/ttt/Screenshot\ from\ 2015-03-24\ 21:47:37.png SegvAnalysis: Segfault happened at: 0x7f65834e0900:mov(%rdi),%rax PC (0x7f65834e0900) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: shotwell 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/gtk-3.0/modules/libunity-gtk-module.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to vivid on 2014-05-04 (324 days ago) UserGroups: adm autopilot cdrom dip libvirtd lpadmin minidlna plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1436072/+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 1431582] Re: there is no wi-fi after suspend/hybernate mode
Are you going something with this bug? In each last few releases you broke something in my notebook. Now are you just a clowns or you have an argue with Asus? -- 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/1431582 Title: there is no wi-fi after suspend/hybernate mode Status in network-manager package in Ubuntu: Confirmed Bug description: During last three days: after suspend/hybernate mode there is no wi- fi. I have to turn off Network-manager and turn it on again- only after that wi-fi works again ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu10 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 00:56:10 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-18 (510 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static metric 1024 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.18 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 802-11-wireless 1426197268 Пт. 13 марта 2015 00:54:28 yes no /org/freedesktop/NetworkManager/Settings/0 yes wlan0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 k3b 66a32a2c-3eac-46e3-a111-0c63e94bd135 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431582/+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 1433361] Re: shotwell crashed with SIGSEGV in g_signal_emit_valist()
*** This bug is a duplicate of bug 1439026 *** https://bugs.launchpad.net/bugs/1439026 ** This bug is no longer a duplicate of bug 1431121 shotwell crashed with SIGSEGV in gtk_application_impl_handle_window_realize() ** This bug has been marked a duplicate of bug 1439026 /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1433361 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() Status in shotwell package in Ubuntu: New Bug description: I was cropping a photo when this happens, but there was no visible problem. I'm pretty sure I already reported this bug once but I didn't see it, so this might be a duplicate. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: shotwell 0.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Mar 17 16:50:07 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2015-03-03 (14 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: shotwell /home/username/Captura\ de\ pantalla\ de\ 2015-03-17\ 16:49:23.png SegvAnalysis: Segfault happened at: 0x7f91814af950:mov(%rdi),%rax PC (0x7f91814af950) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: shotwell 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/gtk-3.0/modules/libunity-gtk-module.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1433361/+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 1431441] Re: shotwell crashed with SIGSEGV in g_signal_emit_valist()
*** This bug is a duplicate of bug 1439026 *** https://bugs.launchpad.net/bugs/1439026 ** This bug is no longer a duplicate of bug 1431121 shotwell crashed with SIGSEGV in gtk_application_impl_handle_window_realize() ** This bug has been marked a duplicate of bug 1439026 /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1431441 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() Status in shotwell package in Ubuntu: New Bug description: Not sure what caused it ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: shotwell 0.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 12 16:12:41 2015 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2014-04-19 (327 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcCmdline: shotwell /home/username/Pictures/Old\ Images/Picture\ Name.jpeg SegvAnalysis: Segfault happened at: 0x7fc5c78d4950:mov(%rdi),%rax PC (0x7fc5c78d4950) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: shotwell 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/gtk-3.0/modules/libunity-gtk-module.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to vivid on 2015-03-02 (9 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1431441/+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 1439007] Re: Cannot open settings
Removing pantheon didn't help, now gnome-control-center executable seems to be missing, even though gnome-control-center package is installed. Settings still don't open. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1439007 Title: Cannot open settings Status in gnome-control-center package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: GNOME settings don't open. When you attempt to open settings through the UI nothing happens. Steps to reproduce 1. Click on the top right corner in GNOME shell 2. Click on the settings icon 3. Settings don't open Expected result: GNOME settings window opened. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-settings-daemon 3.14.2-3ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Apr 1 11:34:35 2015 InstallationDate: Installed on 2015-03-21 (10 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150320) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) upstart.gnome-settings-daemon.log: ** (gnome-settings-daemon:2209): WARNING **: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1439007/+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 1438957] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1431041 *** https://bugs.launchpad.net/bugs/1431041 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1431041, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1438957/+attachment/4362471/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1438957/+attachment/4362474/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1438957/+attachment/4362481/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1438957/+attachment/4362483/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1438957/+attachment/4362484/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1438957/+attachment/4362485/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1438957/+attachment/4362486/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1431041 cups-browsed crashed with SIGSEGV in timeout_free() ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1438957 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() Status in cups-filters package in Ubuntu: New Bug description: This occurred on boot. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CrashCounter: 1 CupsErrorLog: Date: Mon Mar 30 21:38:20 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-03-15 (16 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150314) Lpstat: device for HP-Officejet-Pro-8100: hp:/net/Officejet_Pro_8100?ip=192.168.1.241 device for PDF: cups-pdf:/ MachineType: TOSHIBA Satellite C55D-A Papersize: letter PpdFiles: HP-Officejet-Pro-8100: HP Officejet Pro 8100, hpcups 3.15.2 PDF: Generic CUPS-PDF Printer ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed root=UUID=b6a678ff-8cee-42c1-aa03-ae411b3e10da ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f972ce2215a:movl $0x1,0xa8(%rax) PC (0x7f972ce2215a) ok source $0x1 ok destination 0xa8(%rax) (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd01/27/2014:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-02U005:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55D-A dmi.product.version: PSCFWU-02U005 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1438957/+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 1390623] Re: VPN with IPv6 connectivity but no IPv6 DNS server results in broken DNS config
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- 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/1390623 Title: VPN with IPv6 connectivity but no IPv6 DNS server results in broken DNS config Status in network-manager package in Ubuntu: Confirmed Bug description: When connecting to a VPN that provides both a default route over IPv4 and IPv6, but only DNS servers over IPv4, you can end up with the IPv4 DNS servers set up as split DNS. When that happens, the user is left without a working DNS configuration. See the attached log file for an example. I think the cause is that the patch for avoiding split DNS on VPNs with default routes[1] stops looking when it finds the first VPN configuration with a default route. If that configuration happens to be the IPv6-side of the VPN connection, then it will still add the IPv4 configuration with split DNS. A workaround is to simply add a IPv6 DNS server to the configuration in addition to the IPv4 DNS servers. In that case, the IPv6 DNS server is added without split DNS. This has been tested with both Ubuntu 14.04 LTS and Xubuntu 14.04. Package versions (on Xubuntu 14.04): network-manager 0.9.8.8-0ubuntu7 network-manager-openvpn 0.9.8.2-1ubuntu4 openvpn 2.3.2-7ubuntu3 [1] http://bazaar.launchpad.net/~network-manager/network- manager/ubuntu/view/head:/debian/patches/dnsmasq-vpn-dns- filtering.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390623/+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 1424263] Re: Broken dependencies
Jim Buzaid solution worked for me AFTER doing HWE upgrade https://wiki.ubuntu.com/Kernel/LTSEnablementStack -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424263 Title: Broken dependencies Status in mesa package in Ubuntu: Confirmed Status in steam package in Ubuntu: Confirmed Bug description: I can not install Steam from Steam website because reported package has broken dependencies. This bug affect any user that will install Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on Linux. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri:i386 (not installed) ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.35 Sat Jan 10 21:27:15 PST 2015 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 21 21:40:49 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:84ac] InstallationDate: Installed on 2015-02-20 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H87 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.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Feb 21 17:22:09 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424263/+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 1415958] Re: Laptop + external display does not suspend on lid close
@Martin, could you clarify what is meant by dock events please? Also exactly what you want me to do in the VT. Currently if I switch to a VT and close the lid then as far as I can tell absolutely nothing happens apart from the laptop monitor switching off. Under Unity the external display briefly blanks and then comes back with windows that were on the laptop moved to the external display, so it is switching to single monitor mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1415958 Title: Laptop + external display does not suspend on lid close Status in unity-settings-daemon package in Ubuntu: New Bug description: Since update to Vivid, laptop does not suspend on lid close if an external monitor is connected, even though suspend is selected in the power settings for lid close. The display flashes and apps move to external display. Syslog shows no attempt to suspend. On Utopic it suspended ok with external monitor. In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are messages in syslog at that time but I suspect they may be a different issue: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment WORKAROUND: Suspend via the menu. WORKAROUND: Disconnect external monitor first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 29 15:04:52 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:17a9] InstallationDate: Installed on 2014-12-27 (33 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 29 15:00:08 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13890 vendor SEC xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1415958/+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 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
** Changed in: xorg (Ubuntu Trusty) Assignee: job (jeppekdahl) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/1400626 Title: Please backport xtrans, libdrm, x11proto-{fonts,core} packages for 14.04.2 Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-snapshot package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in x11proto-fonts package in Ubuntu: Invalid Status in xorg package in Ubuntu: Invalid Status in xtrans package in Ubuntu: Invalid Status in libdrm source package in Trusty: Fix Released Status in llvm-toolchain-snapshot source package in Trusty: Fix Released Status in x11proto-core source package in Trusty: Fix Released Status in x11proto-fonts source package in Trusty: Fix Released Status in xorg source package in Trusty: Fix Released Status in xtrans source package in Trusty: Fix Released Bug description: In order to upload the new xorg-server we need to backport the following packages from utopic: libdrm x11proto-core x11proto-fonts xtrans libdrm 2.4.52-1-2.4.56-1 seems to have the following changes: - Hides private symbols from all libdrm libraries - fixes MSAA on Hawaii (radeon). - Adds cherryview pci-ids (intel). - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd. - Fixes to exynos and freedreno. - Enables building libdrm-freedreno1 and libdrm-exynos1 x11proto-core's main change appears to be changing from the 'pointer' type to 'void *': https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz x11proto-fonts' main change is the same as x11proto-core, but the documentation is reformatted too: https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz xtrans seems to have 2 minor changes, increase default unix pipe size and add support for systemd socket activation: https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz xorg needs to be slightly updated, to allow xserver-xorg to provide the unrenamed lts-utopic, and to allow xorg to be installed with the renamed xorg-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+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 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
** Branch linked: lp:ubuntu/language-selector -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c Status in central project for keyboard configuration: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: New Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: When typing in a US-international keyboard with dead-keys (or UK-international), typing 'c results in an accented c instead of a cedilla. There is a workaround, which is editing the /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules file and changing the line cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa to cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en (add the 'en' at the end). However, every time some update on this file is applied, one looses the change, and we get back to the accented c. That means having to modify the file again, logout and login. For me this is no problem. But for my brother, mom, dad, etc, it is always something that at least makes me less proud of having convinced them to use Ubuntu, because they don't know what to do each time this happens. I think we really need a configurable keyboard layout, or at least (and that would be very easy), the inclusion of alternate layouts on install that for the dead-key options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla. This change is relevant for at least Portuguese and French. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+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 1435269] Re: System does not suspend when lid closed
I have the same problem with my Vivid installation. The laptop is a HP ProBook 470 G0. When I close the lid, there are cases when it suspends, but in most of the cases it doesn't. The journalctl -b is attached, the journalctl -f shows this when the suspend is ok: Apr 01 11:16:47 micsa systemd-logind[1031]: Lid closed. Apr 01 11:16:47 micsa systemd-logind[1031]: Suspending... Apr 01 11:16:47 micsa NetworkManager[999]: info sleep requested (sleeping: no enabled: yes) Apr 01 11:16:47 micsa NetworkManager[999]: info sleeping... Apr 01 11:16:47 micsa NetworkManager[999]: info (wlan0): device state change: activated - unmanaged (reason 'sleeping') [100 10 37] Apr 01 11:16:47 micsa NetworkManager[999]: info (wlan0): deactivating device (reason 'sleeping') [37] Apr 01 11:16:47 micsa kernel: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Apr 01 11:16:47 micsa NetworkManager[999]: info (wlan0): canceled DHCP transaction, DHCP client pid 8820 Apr 01 11:16:47 micsa avahi-daemon[1011]: Withdrawing address record for fe80::4a51:b7ff:fe15:5b26 on wlan0. Apr 01 11:16:47 micsa avahi-daemon[1011]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::4a51:b7ff:fe15:5b26. Apr 01 11:16:47 micsa avahi-daemon[1011]: Interface wlan0.IPv6 no longer relevant for mDNS. Apr 01 11:16:47 micsa kernel: wlan0: deauthenticating from e8:de:27:f6:c5:dc by local choice (Reason: 3=DEAUTH_LEAVING) Apr 01 11:16:47 micsa wpa_supplicant[1466]: wlan0: CTRL-EVENT-DISCONNECTED bssid=e8:de:27:f6:c5:dc reason=3 locally_generated=1 Apr 01 11:16:47 micsa avahi-daemon[1011]: Withdrawing address record for 192.168.1.175 on wlan0. Apr 01 11:16:47 micsa avahi-daemon[1011]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.175. Apr 01 11:16:47 micsa kernel: cfg80211: Calling CRDA to update world regulatory domain Apr 01 11:16:47 micsa avahi-daemon[1011]: Interface wlan0.IPv4 no longer relevant for mDNS. Apr 01 11:16:47 micsa NetworkManager[999]: info Writing DNS information to /sbin/resolvconf and this, when the suspend is not ok: Apr 01 11:22:53 micsa systemd-logind[1003]: Lid closed. Apr 01 11:22:53 micsa kernel: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Apr 01 11:22:53 micsa kernel: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Apr 01 11:22:58 micsa bluetoothd[988]: bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/HFPAG Apr 01 11:22:58 micsa bluetoothd[988]: bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/HFPHS Apr 01 11:22:58 micsa bluetoothd[988]: bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/A2DPSource Apr 01 11:22:58 micsa bluetoothd[988]: bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/A2DPSink Apr 01 11:22:58 micsa bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/HFPAG Apr 01 11:22:58 micsa bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/HFPHS Apr 01 11:22:58 micsa bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/A2DPSource Apr 01 11:22:58 micsa bluetoothd[988]: Endpoint unregistered: sender=:1.71 path=/MediaEndpoint/BlueZ4/A2DPSink Apr 01 11:22:59 micsa ntpdate[3186]: adjust time server 91.189.89.199 offset 0.038673 sec Apr 01 11:22:59 micsa org.gnome.zeitgeist.Engine[2383]: ** (zeitgeist-datahub:3243): WARNING **: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datah ub on the bus! Apr 01 11:23:00 micsa systemd-logind[1003]: Lid opened. Apr 01 11:23:00 micsa kernel: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment or this: Apr 01 11:19:50 micsa systemd-logind[980]: Lid closed. Apr 01 11:19:50 micsa kernel: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Apr 01 11:19:50 micsa kernel: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Apr 01 11:19:54 micsa gnome-session[2741]: WARN 2015-04-01 11:19:54 nux.inputmethod.ibus InputMethodIBus.cpp:63 Impossible to connect to connect to ibus Apr 01 11:19:54 micsa gnome-session[2741]: WARN 2015-04-01 11:19:54 unity.dash.gsettingsscopereader GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: s ocial.scope : Valid key file could not be found in search dirs Apr 01 11:19:57 micsa systemd-logind[980]: Lid opened. Apr 01 11:19:57 micsa kernel: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment Apr 01 11:20:01 micsa CRON[3380]: pam_unix(cron:session): session opened for user root by (uid=0) gdbus call --system -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.ListInhibitors ([('handle-power-key:handle-suspend-key:handle-hibernate-key', 'micsa', 'GNOME handling keypresses', 'block', uint32 1000, uint32 2487), ('sleep', 'Unity Lockscreen', 'Unity wants
[Desktop-packages] [Bug 1438917] Re: cups-browsed crashed with SIGABRT in __malloc_assert()
*** This bug is a duplicate of bug 1435611 *** https://bugs.launchpad.net/bugs/1435611 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1435611, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1438917/+attachment/4362406/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1438917/+attachment/4362410/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1438917/+attachment/4362418/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1438917/+attachment/4362420/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1438917/+attachment/4362421/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1438917/+attachment/4362422/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1438917/+attachment/4362423/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1435611 cups-browsed crashed with SIGABRT in __malloc_assert() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1438917 Title: cups-browsed crashed with SIGABRT in __malloc_assert() Status in cups-filters package in Ubuntu: New Bug description: Hello, Anything wrong ? Not for me. I don't know why there is a bug report. I am a simple user and I saw nothing wrong and can't speak english well. I like the vivid vervet beta2 version! It works for me. I apologize for making you waste your time. p. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Mar 31 22:46:08 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-03-29 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK Computer Inc. F50Q Papersize: a4 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __malloc_assert (assertion=assertion@entry=0x7f5faed23560 (unsigned long) (size) = (unsigned long) (nb), file=file@entry=0x7f5faed1f282 malloc.c, line=line@entry=3689, function=function@entry=0x7f5faed1f60a __func__.11519 _int_malloc) at malloc.c:297 _int_malloc (av=av@entry=0x7f5faef56c00 main_arena, bytes=bytes@entry=48) at malloc.c:3689 __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3213 ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2 ippAddInteger () from /usr/lib/x86_64-linux-gnu/libcups.so.2 Title: cups-browsed crashed with SIGABRT in __malloc_assert() UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/07/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F50Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr211:bd04/07/2009:svnASUSTeKComputerInc.:pnF50Q:pvr1.0:rvnASUSTeKComputerInc.:rnF50Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F50Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1438917/+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 1415958] Re: Laptop + external display does not suspend on lid close
For the record, systemd actually checks for docked/undocked events, so in a VT you should not actually get this behaviour. Only under Unity, because unity-settings-daemon doesn't seem to check for dock events in particular but just checks the connected monitors. Can you confirm this? ** Package changed: xorg (Ubuntu) = unity-settings-daemon (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/1415958 Title: Laptop + external display does not suspend on lid close Status in unity-settings-daemon package in Ubuntu: New Bug description: Since update to Vivid, laptop does not suspend on lid close if an external monitor is connected, even though suspend is selected in the power settings for lid close. The display flashes and apps move to external display. Syslog shows no attempt to suspend. On Utopic it suspended ok with external monitor. In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are messages in syslog at that time but I suspect they may be a different issue: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment WORKAROUND: Suspend via the menu. WORKAROUND: Disconnect external monitor first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 29 15:04:52 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:17a9] InstallationDate: Installed on 2014-12-27 (33 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 29 15:00:08 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13890 vendor SEC xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1415958/+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 1105171] Re: X.Org is stuck in a loop on resume from S3
Reverting job (jeppekdahl)'s changes. -- 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/1105171 Title: X.Org is stuck in a loop on resume from S3 Status in amd: New Status in fglrx-installer package in Ubuntu: Incomplete Bug description: X.Org is stuck in a loop on resume from S3. Only doing Alt+Sysrq+K kills X and allows the system to go back to the login screen. When it was stuck in the loop I could clearly see the laptop backlight being switched on and off while the screen remained black. Note: installing xserver-xorg-lts-precise (and keeping the backported kernel) solves the issue ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise2 ProcVersionSignature: Ubuntu 3.5.0-22.34~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Jan 25 16:00:45 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130125) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg-server-lts-quantal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1105171/+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 1362848] Re: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze
I had the same problem; I discovered I was mixing trusty xorg with utopic kernel... upgrading both to utopic solved the problem: https://wiki.ubuntu.com/Kernel/LTSEnablementStack -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1362848 Title: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89 from Additional Drivers application then reboot, it shows black screen, no login window, I even can't use ctrl+alt+F2 to switch to text mode, then I reboot and go to recovery mode, use 'prime-select intel' to switch to intel GPU and reboot, everything is fine, but as soon as I switch to nvidia GPU, still same issue. OS: Ubuntu 14.04 64bit Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600 Desktop: Unity Kernel: 3.13.0 CPU: Intel® Core™ i7-4700MQ Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/+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 1438904] Re: shotwell crashed with SIGSEGV in g_signal_emit_valist()
*** This bug is a duplicate of bug 1439026 *** https://bugs.launchpad.net/bugs/1439026 ** This bug is no longer a duplicate of bug 1431121 shotwell crashed with SIGSEGV in gtk_application_impl_handle_window_realize() ** This bug has been marked a duplicate of bug 1439026 /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1438904 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() Status in shotwell package in Ubuntu: New Bug description: opening a picture! ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: shotwell 0.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 31 22:11:45 2015 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2014-09-16 (196 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcCmdline: shotwell /home/username/Scrivania/40790_1539284131106_682007_n.jpg ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f4c5ef7ea40:mov(%rdi),%rax PC (0x7f4c5ef7ea40) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: shotwell 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/gtk-3.0/modules/libunity-gtk-module.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to vivid on 2015-03-11 (20 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1438904/+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 1438779] Re: shotwell crashed with SIGSEGV in g_signal_emit_valist()
*** This bug is a duplicate of bug 1439026 *** https://bugs.launchpad.net/bugs/1439026 ** This bug is no longer a duplicate of bug 1431121 shotwell crashed with SIGSEGV in gtk_application_impl_handle_window_realize() ** This bug has been marked a duplicate of bug 1439026 /usr/bin/shotwell:11:gtk_application_impl_handle_window_realize:gtk_window_realize:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1438779 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() Status in shotwell package in Ubuntu: New Bug description: --- ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: shotwell 0.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 31 17:40:43 2015 ExecutablePath: /usr/bin/shotwell InstallationDate: Installed on 2014-05-07 (328 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. ProcCmdline: shotwell /home/username/Scrivania/Schermata\ del\ 2015-03-31\ 17:38:48.png SegvAnalysis: Segfault happened at: 0x7fe26fd07a40:mov(%rdi),%rax PC (0x7fe26fd07a40) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: shotwell 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/gtk-3.0/modules/libunity-gtk-module.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: shotwell crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: Upgraded to vivid on 2015-03-30 (1 days ago) UserGroups: sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1438779/+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 1300235] Re: init (chromium-browser) crashed with SIGSEGV
** Branch linked: lp:apport -- 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/1300235 Title: init (chromium-browser) crashed with SIGSEGV Status in apport package in Ubuntu: Fix Committed Status in chromium-browser package in Ubuntu: Triaged Bug description: Test Case - 1) Set your default browser to Chromium. 2) Launch synaptic 3) Click on the home page url for a package. 4) Observe chromium-browser not launch 5) Receive apport crash dialog 5) Also notice the apport crash dialog refers to upstart / systemd none ProblemType: CrashDistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Mon Mar 31 09:53:16 2014 Disassembly: = 0x7fa2b65e94d7: Cannot access memory at address 0x7fa2b65e94d7 ExecutablePath: /sbin/init InstallationDate: Installed on 2014-03-05 (25 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305) ProcCmdline: /sbin/init ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash SegvAnalysis: Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 0x7fa2b65e94d7 PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)! Stack pointer not within stack segment SegvReason: executing unknown VMA Signal: 11SourcePackage: upstart StacktraceTop: ?? () ?? () ?? () Title: init crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.12.1) UserGroups: modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1300235/+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 1300235] Re: init (chromium-browser) crashed with SIGSEGV
Apport fixed upstream in r2941, thanks Brian! ** Changed in: apport (Ubuntu) Status: Triaged = Fix Committed ** Changed in: apport (Ubuntu) Assignee: (unassigned) = Brian Murray (brian-murray) -- 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/1300235 Title: init (chromium-browser) crashed with SIGSEGV Status in apport package in Ubuntu: Fix Committed Status in chromium-browser package in Ubuntu: Triaged Bug description: Test Case - 1) Set your default browser to Chromium. 2) Launch synaptic 3) Click on the home page url for a package. 4) Observe chromium-browser not launch 5) Receive apport crash dialog 5) Also notice the apport crash dialog refers to upstart / systemd none ProblemType: CrashDistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Mon Mar 31 09:53:16 2014 Disassembly: = 0x7fa2b65e94d7: Cannot access memory at address 0x7fa2b65e94d7 ExecutablePath: /sbin/init InstallationDate: Installed on 2014-03-05 (25 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305) ProcCmdline: /sbin/init ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash SegvAnalysis: Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 0x7fa2b65e94d7 PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)! Stack pointer not within stack segment SegvReason: executing unknown VMA Signal: 11SourcePackage: upstart StacktraceTop: ?? () ?? () ?? () Title: init crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.12.1) UserGroups: modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1300235/+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 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
To make it easier to keep discussing this issue, I committed a change to language-selector, which hopefully is a step in the right direction. ** Changed in: language-selector (Ubuntu) Importance: Undecided = Medium ** Changed in: language-selector (Ubuntu) Status: New = Fix Committed ** Changed in: language-selector (Ubuntu) Assignee: (unassigned) = Gunnar Hjalmarsson (gunnarhj) ** Changed in: gtk+2.0 (Ubuntu) Importance: Low = Medium ** Changed in: xkeyboard-config (Ubuntu) Importance: Wishlist = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c Status in central project for keyboard configuration: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Fix Committed Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: When typing in a US-international keyboard with dead-keys (or UK-international), typing 'c results in an accented c instead of a cedilla. There is a workaround, which is editing the /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules file and changing the line cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa to cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en (add the 'en' at the end). However, every time some update on this file is applied, one looses the change, and we get back to the accented c. That means having to modify the file again, logout and login. For me this is no problem. But for my brother, mom, dad, etc, it is always something that at least makes me less proud of having convinced them to use Ubuntu, because they don't know what to do each time this happens. I think we really need a configurable keyboard layout, or at least (and that would be very easy), the inclusion of alternate layouts on install that for the dead-key options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla. This change is relevant for at least Portuguese and French. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+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 1439006] Re: [FFe] Install Fcitx for Japanese users
@Iain: Otherwise there would in effect be a regression with respect to the Japanese remix. It has been shipped with fcitix as the default IM framework, making use of the old im-config behavior. The new im-config behavior, which is locale based, breaks that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1439006 Title: [FFe] Install Fcitx for Japanese users Status in im-config package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: According to my proposal [1], Fcitx should be default for Japanese uses on Vivid release cycle. https://lists.ubuntu.com/archives/ubuntu-desktop/2015-March/004645.html Ref: https://bugs.launchpad.net/ubuntu/+source/language- selector/+bug/1430893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1439006/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
** Also affects: unity Importance: Undecided Status: New ** Tags added: lockscreen ** Changed in: unity (Ubuntu Trusty) Importance: Undecided = High ** Changed in: unity Importance: Undecided = High ** Changed in: unity (Ubuntu Vivid) Importance: Undecided = High ** Changed in: unity (Ubuntu Utopic) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in Unity: New Status in unity package in Ubuntu: New Status in unity source package in Trusty: New Status in unity source package in Utopic: New Status in unity source package in Vivid: New Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver' 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438870/+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 1415958] Re: Laptop + external display does not suspend on lid close
More evidence, of a rather confusing nature. With default /etc/systemd/logind.conf (which has everything commented out). With only the laptop display Unity and VT both suspend ok when lid is closed With laptop display + external display Neither Unity nor VT suspend when lid is closed. With HandleLidSwitchDocked=suspend in /etc/systemd/logind.conf With only the laptop display Unity and VT both suspend ok when lid is closed With laptop display + external display Unity does not suspend the first time the lid is closed, but does the second, in fact it suspends every second time the lid is closed (though not absolutely sure this is completely consistent). I think once it was not till the third time that it suspended. VT suspends ok when lid is closed. This is software so there is some sense there somewhere. It is just a matter of finding it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1415958 Title: Laptop + external display does not suspend on lid close Status in unity-settings-daemon package in Ubuntu: New Bug description: Since update to Vivid, laptop does not suspend on lid close if an external monitor is connected, even though suspend is selected in the power settings for lid close. The display flashes and apps move to external display. Syslog shows no attempt to suspend. On Utopic it suspended ok with external monitor. In the logs the lid was closed on Jan 29 15:04:00 and opened at 15:04:30. There are messages in syslog at that time but I suspect they may be a different issue: i915 :00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment WORKAROUND: Suspend via the menu. WORKAROUND: Disconnect external monitor first. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 29 15:04:52 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:17a9] InstallationDate: Installed on 2014-12-27 (33 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141227) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=09bfc4b3-c846-47be-ba86-c3db22bcff54 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd05/09/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 29 15:00:08 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13890 vendor SEC xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1415958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Attachment added: dmesg with the latest Xorg packages and with Upstart https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1434036/+attachment/4362792/+files/dmesg-AMIGA_one_X1000_Upstart_with_latest_Xorg_packages.log -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us.
[Desktop-packages] [Bug 1435269] Re: System does not suspend when lid closed
another thing: the sudo systemctl suspend seems to be working... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1435269 Title: System does not suspend when lid closed Status in unity-settings-daemon package in Ubuntu: New Bug description: Under Utopic closing the laptop lid would suspend the system. Since a Vivid upgrade this no longer happens (the external screen goes blank for about a second, then the desktop comes back as before) The system power settings show When lid is closed: suspend as before, it just gets ignored. The menu suspend option does suspend correctly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 23 10:49:19 2015 InstallationDate: Installed on 2014-11-29 (113 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20344 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN25WW(V1.11) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN25WW(V1.11):bd07/09/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1435269/+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 1424491] Re: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5
I'm working on it. You can expect an update soon. ** Also affects: fglrx-installer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: fglrx-installer-updates (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: fglrx-installer (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: fglrx-installer-updates (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: fglrx-installer-updates (Ubuntu Trusty) Status: New = In Progress ** Changed in: fglrx-installer (Ubuntu Trusty) Status: New = In Progress ** Changed in: fglrx-installer-updates (Ubuntu Trusty) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer (Ubuntu Trusty) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer (Ubuntu Trusty) Status: In Progress = Triaged ** Changed in: fglrx-installer-updates (Ubuntu Precise) Status: New = Triaged ** Changed in: fglrx-installer-updates (Ubuntu Precise) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer (Ubuntu Precise) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer (Ubuntu) Status: In Progress = Invalid ** Changed in: fglrx-installer-updates (Ubuntu) Status: In Progress = Invalid ** Changed in: fglrx-installer-updates (Ubuntu Trusty) Importance: Undecided = High ** Changed in: fglrx-installer (Ubuntu Trusty) Importance: Undecided = High ** Changed in: fglrx-installer (Ubuntu Precise) Status: New = Triaged ** Changed in: fglrx-installer (Ubuntu Precise) Importance: Undecided = High ** Changed in: fglrx-installer-updates (Ubuntu Precise) Importance: Undecided = High ** Changed in: fglrx-installer (Ubuntu Trusty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1424491 Title: apt-get fails to install fglrx or fglrx-updates in 14.04.2 and 12.04.5 Status in AMD fglrx video driver: Invalid Status in fglrx-installer package in Ubuntu: Invalid Status in fglrx-installer-updates package in Ubuntu: Invalid Status in fglrx-installer source package in Precise: Triaged Status in fglrx-installer-updates source package in Precise: Triaged Status in fglrx-installer source package in Trusty: In Progress Status in fglrx-installer-updates source package in Trusty: In Progress Bug description: Activity: Install fglrx AMD driver on 12.04.5 and 14.02.2 Expected behavior: fglrx would intall Observed behavior: fglrx is not installed as follows Attempt to install fglrx fails as follows: zack3@ZACK3:~$ sudo apt-get install fglrx-updates xvba-va-driver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: fglrx-updates : Depends: xorg-video-abi-11 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-15 E: Unable to correct problems, you have held broken packages. Attempt to insatll xorg-video-abi-15 yields: zack3@ZACK3:~$ sudo apt-get install xorg-video-abi-15 Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xserver-xorg-core' instead of 'xorg-video-abi-15' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Attachment added: dmesg with the latest Xorg packages and with systemd https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1434036/+attachment/4362738/+files/dmesg-AMIGA_one_X1000.log -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us. Thanks in advance. Cheers,
[Desktop-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
Hi Sebastien, which package version contains the fix? -- 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/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1396361] Re: Double Mouse Cursor
pauljohn32, it would help immensely if you filed a new report via a terminal: ubuntu-bug xorg Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Also, please feel free to subscribe me to it. ** Tags removed: apport-collected ubuntu ** Attachment removed: xdpyinfo.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362560/+files/xdpyinfo.txt ** Attachment removed: Xrandr.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362559/+files/Xrandr.txt ** Attachment removed: XorgLogOld.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362558/+files/XorgLogOld.txt ** Attachment removed: XorgLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362557/+files/XorgLog.txt ** Attachment removed: UdevLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362555/+files/UdevLog.txt ** Attachment removed: UnitySupportTest.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362556/+files/UnitySupportTest.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362554/+files/UdevDb.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362553/+files/ProcModules.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362552/+files/ProcInterrupts.txt ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362551/+files/ProcEnviron.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362550/+files/ProcCpuinfo.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362549/+files/Lsusb.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362548/+files/Lspci.txt ** Attachment removed: LightdmLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362547/+files/LightdmLog.txt ** Attachment removed: LightdmGreeterLogOld.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362546/+files/LightdmGreeterLogOld.txt ** Attachment removed: LightdmGreeterLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362545/+files/LightdmGreeterLog.txt ** Attachment removed: LightdmDisplayLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362544/+files/LightdmDisplayLog.txt ** Attachment removed: GconfCompiz.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362543/+files/GconfCompiz.txt ** Attachment removed: DpkgLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362542/+files/DpkgLog.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362540/+files/CurrentDmesg.txt ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362541/+files/Dependencies.txt ** Attachment removed: BootLog.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362539/+files/BootLog.txt ** Attachment removed: BootDmesg.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361/+attachment/4362538/+files/BootDmesg.txt -- 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/1396361 Title: Double Mouse Cursor Status in xorg package in Ubuntu: Incomplete Bug description: When dragging with the mouse cursor often it creates a double cursor side by side about 10 cm apart on the screen. Only one cursor works. Using print screen does not show the cursor in the resulting image. Rebooting corrects the problem. This is similar to the double mouse cursor reported as a result of flash in a browser, however the current problem will occur without the browser open. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 25 15:58:51 2014 InstallationDate: Installed on 2014-10-24 (32 days ago) InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Attachment added: Xorg.0.log with the latest Xorg packages and with systemd https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1434036/+attachment/4362739/+files/Xorg.0-AMIGA_one_X1000.log -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us. Thanks in advance. Cheers,
[Desktop-packages] [Bug 1420934] Re: [online-accounts] re-authenticating an account does not work
This bug was fixed in the package sync-monitor - 0.1+15.04.20150327-0ubuntu1 --- sync-monitor (0.1+15.04.20150327-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Renato Araujo Oliveira Filho ] * Created sync-monitor-helper to re-authenticate accounts. (LP: #1420934) -- CI Train Bot ci-train-...@canonical.com Fri, 27 Mar 2015 11:13:09 + ** Changed in: sync-monitor (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-plugin-oauth2 in Ubuntu. https://bugs.launchpad.net/bugs/1420934 Title: [online-accounts] re-authenticating an account does not work Status in the base for Ubuntu mobile products: Fix Committed Status in signon-plugin-oauth2 package in Ubuntu: Fix Committed Status in sync-monitor package in Ubuntu: Fix Released Status in signon-plugin-oauth2 package in Ubuntu RTM: Fix Committed Bug description: After a online account token became invalid we should use the function AccountService.authenticate to re-validate the account. But is is not working for google accounts. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Attachment added: syslog with the latest Xorg packages and with systemd https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1434036/+attachment/4362741/+files/syslog-AMIGA_one_X1000 -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us. Thanks in advance. Cheers,
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
** Attachment added: kern.log with the latest Xorg packages and with systemd https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1434036/+attachment/4362740/+files/kern-AMIGA_one_X1000.log -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0) -- I installed Upstart again but unfortunately it didn't solve the problem with the black screen and the blink cursor. The temporary solution is to downgrade Xorg: sudo dpkg -i xserver-xorg-core_1.16.0-1ubuntu1.3_powerpc.deb sudo dpkg -i xserver-xorg-video-radeon_7.4.0-2ubuntu2_powerpc.deb sudo dpkg -i xserver-xorg-video-ati_7.4.0-2ubuntu2_powerpc.deb I created a package with all debs and Mesa libs for the downgrade last week. Download: http://www.xenosoft.de/Xorg_and_unofficial_Mesa_for_ubuntu_MATE_15.04_AMIGA_one_X1000.tar.gz Further information: http://ubuntuforums.org/showthread.php?t=2264322 PLEASE help us. Thanks in advance. Cheers,
[Desktop-packages] [Bug 1439076] Re: remmina crashed with SIGSEGV in freerdp_channels_find_by_open_handle()
*** This bug is a duplicate of bug 1425743 *** https://bugs.launchpad.net/bugs/1425743 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1425743, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1439076/+attachment/4362754/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1439076/+attachment/4362756/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1439076/+attachment/4362758/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1439076/+attachment/4362759/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1439076/+attachment/4362760/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1439076/+attachment/4362762/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1439076/+attachment/4362763/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1425743 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1439076 Title: remmina crashed with SIGSEGV in freerdp_channels_find_by_open_handle() Status in remmina package in Ubuntu: New Bug description: Reminna crashes on me once or twice a day. I use it a lot; I think it is one of the most important linux programs for someone who administers windows networks. Anyway this is just another crash that happened. Reminna is one application that I wish got heaver funding. This really needs to be rock solid for everyone. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: remmina 1.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Apr 1 04:12:58 2015 ExecutablePath: /usr/bin/remmina ProcCmdline: remmina -i ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: remmina StacktraceTop: freerdp_channels_find_by_open_handle () from /usr/lib/x86_64-linux-gnu/libfreerdp-client.so.1.1 FreeRDP_VirtualChannelWrite () from /usr/lib/x86_64-linux-gnu/libfreerdp-client.so.1.1 svc_plugin_send () from /usr/lib/x86_64-linux-gnu/libfreerdp-utils.so.1.1 ?? () from /usr/lib/x86_64-linux-gnu/libfreerdp-client.so.1.1 ?? () from /usr/lib/x86_64-linux-gnu/libfreerdp-utils.so.1.1 Title: remmina crashed with SIGSEGV in freerdp_channels_find_by_open_handle() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1439076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434036] Re: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update
Adam Smith (adamsmith) wrote 19 hours ago: -- There are a lot of unhandled signal 11 errors in those logs - could you confirm if you all have those so we're talking about the same error? If downgrading the xorg packages fixes those errors Yes, the downgrade fixes the signal 11 errors. I figured out that I have a lot of signal 11 error messages with systemd. With Upstart I have only 4 signal 11 errors: [9.371697] lightdm-gtk-gre[2731]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 [ 14.367464] lightdm-gtk-gre[3000]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 [ 20.591891] lightdm-gtk-gre[3219]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 [ 26.831432] lightdm-gtk-gre[3533]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 With systemd, X11 starts again and again with a white screen. With Upstart I have a black screen with a blink cursor. -- 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/1434036 Title: ubuntu MATE 15.04 PPC/Lubuntu 15.04 PPC Xorg: Only black screen with blink cursor after update Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Confirmed Bug description: Hi All, We updated ubuntu MATE 15.04 and Lubuntu 15.04 on our PowerPC computers (Power Mac G5 Quad and AMIGA one X1000) last week. Synaptic told us that it want to remove xserver-xorg-video-radeon and xserver- xorg-video-ati. But there are new versions available (xserver-xorg- video-radeon 1:7.5.0-1ubuntu2 and xserver-xorg-video-ati 1:7.5.0-1ubuntu2). Synaptic removed both old packages and Xorg didn't work after that. I selected both new packages and updated them manually. After a restart I had a black screen with a blink cursor. There aren't any error messages in the log file '/var/log/Xorg.0.log' but I found some error messages in the log file '/var/log/syslog': . Exiting. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:41 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:41 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:41 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:41 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:41 ubuntu lightdm[20218]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:42 ubuntu systemd[1]: Started Session c109 of user lightdm. Mar 19 11:45:42 ubuntu systemd[1]: Starting Session c109 of user lightdm. Mar 19 11:45:42 ubuntu lightdm[20218]: ** (lightdm:20218): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:43 ubuntu kernel: lightdm-gtk-gre[20251]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: A connection to the bus can't be made Mar 19 11:45:44 ubuntu org.gtk.vfs.Daemon[20250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE Mar 19 11:45:44 ubuntu systemd[1]: Unit lightdm.service entered failed state. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service failed. Mar 19 11:45:44 ubuntu systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 19 11:45:44 ubuntu systemd[1]: Starting Light Display Manager... Mar 19 11:45:44 ubuntu systemd[1]: Started Light Display Manager. Mar 19 11:45:44 ubuntu lightdm[20381]: initctl: Verbindung zu Upstart nicht möglich: Failed to connect to socket /com/ubuntu/upstart: Verbindungsaufbau abgelehnt Mar 19 11:45:45 ubuntu systemd[1]: Started Session c110 of user lightdm. Mar 19 11:45:45 ubuntu systemd[1]: Starting Session c110 of user lightdm. Mar 19 11:45:45 ubuntu lightdm[20381]: ** (lightdm:20381): WARNING **: Error using VT_WAITACTIVE 7 on /dev/console: No such device or address Mar 19 11:45:46 ubuntu kernel: lightdm-gtk-gre[20414]: unhandled signal 11 at nip 6f4e61c4 lr 6f4e619c code 30001 Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: A connection to the bus can't be made Mar 19 11:45:46 ubuntu org.gtk.vfs.Daemon[20413]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0)
[Desktop-packages] [Bug 1294822] Re: nautilus crashed with SIGSEGV in nautilus_window_sync_location_widgets()
*** This bug is a duplicate of bug 1371220 *** https://bugs.launchpad.net/bugs/1371220 ** This bug has been marked a duplicate of private bug 1371220 -- 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/1294822 Title: nautilus crashed with SIGSEGV in nautilus_window_sync_location_widgets() Status in nautilus package in Ubuntu: New Bug description: In nautilus open a lot of tabs. Close using x. Get apport window. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 19 20:07:26 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2013-10-15 (154 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131015) ProcCmdline: nautilus -n ProcEnviron: LANGUAGE=pl PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x479ee9: cmp%rax,(%rdx) PC (0x00479ee9) ok source %rax ok destination (%rdx) (0x6cd063900) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () ?? () 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 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to trusty on 2013-11-05 (134 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo usr_lib_nautilus: brasero3.10.0-0ubuntu1 evince 3.10.3-0ubuntu10 file-roller3.10.2.1-0ubuntu4 nautilus-share 0.7.3-1ubuntu5 totem 3.10.1-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1294822/+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 1439084] [NEW] Install button missing in Extensions menue
Public bug reported: To install an extension directly from a file on the local hard disk, the documentation on http://kb.mozillazine.org/Extensions_%28Thunderbird%29 reads: Press the Install button in Tools - Extensions (it's Tools - Add-ons - Extensions in 2.0) in Thunderbird. (In newer versions of Thunderbird, click on the Gear icon to access this function and others.) However, there is no install button. I managed finally to install the plugin by drag and drop from nautilus after searching the web, but this is nowhere documented. Removal of that that button was in my opiniton once again a rather unnecessary but for useres very annoying interface change. At least the documentation should be updated. Opening the XPI with thunderbird by the way just creates and empty mail with the xpi as attachment, I think that's acceptable in that case, as this behaviour will be desired for most files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BuildID: 20150223201941 Channel: Unavailable CurrentDesktop: GNOME Date: Wed Apr 1 11:20:47 2015 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-03-18 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1) IpRoute: default via 10.75.15.254 dev eth1 proto static 10.75.0.0/20 dev eth1 proto kernel scope link src 10.75.10.172 metric 1 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-b335e522-6d32-40f8-948c-cb7c32150321 PrefErrors: 'utf-8' codec can't decode byte 0xe4 in position 849: invalid continuation byte PrefSources: [Profile]/extensions/EditMailSubject@jcp.convenant/defaults/preferences/preferences.js [Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js Profiles: Profile0 (Default) - LastVersion=31.5.0/20150223201941 (In use) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: gnome-shell 3.10.4-0ubuntu5.2 rhythmbox-mozilla 3.0.2-0ubuntu2 totem-mozilla 3.10.1-1ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-b335e522-6d32-40f8-948c-cb7c32150321 bp-6aafced0-baf0-4aeb-bb78-76db42130710 bp-2f33ee93-ebef-4c78-9820-a5ef02130604 bp-165d47e2-3d48-48b0-a54c-08d672121202 bp-14749f5b-fbb0-4861-bb01-e27a72121119 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1439084 Title: Install button missing in Extensions menue Status in thunderbird package in Ubuntu: New Bug description: To install an extension directly from a file on the local hard disk, the documentation on http://kb.mozillazine.org/Extensions_%28Thunderbird%29 reads: Press the Install button in Tools - Extensions (it's Tools - Add- ons - Extensions in 2.0) in Thunderbird. (In newer versions of Thunderbird, click on the Gear icon to access this function and others.) However, there is no install button. I managed finally to install the plugin by drag and drop from nautilus after searching the web, but this is nowhere documented. Removal of that that button was in my opiniton once again a rather unnecessary but for useres very annoying interface change. At least the documentation should be
[Desktop-packages] [Bug 1430093] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
https://errors.ubuntu.com/problem/a69a395811666090e103b1a48890e12ef0b433b5 ** Changed in: nautilus (Ubuntu) Status: New = Triaged ** Changed in: nautilus (Ubuntu) Importance: Medium = High -- 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/1430093 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_a() Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: Close and Crash. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu4 Uname: Linux 4.0.0-04rc3-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Mar 9 22:14:31 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-09-25 (166 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140923) ProcCmdline: nautilus -n SegvAnalysis: Segfault happened at: 0x7f2392b94f1f g_type_check_instance_is_a+63: testb $0x4,0x16(%rax) PC (0x7f2392b94f1f) ok source $0x4 ok destination 0x16(%rax) (0xe83f8b48fb894866) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1430093/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
org.gnome.Nautilus.desktop also doesn't have any of the right-click menu bookmarks. that was an issue in nautilus, I just uploaded a fix for it ** Changed in: nautilus (Ubuntu) Status: Fix Released = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1422424] Re: week 13 duplicate
Same here (on linux mint), but weeks are wrong until 43. The version of evolution-data-server here is 3.6.2-0ubuntu0.2 $ uname -a Linux ricab-desktopCERN 3.5.0-51-generic #77~precise1-Ubuntu SMP Thu Jun 5 00:47:34 UTC 2014 i686 i686 i686 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1422424 Title: week 13 duplicate Status in evolution-data-server package in Ubuntu: Confirmed Bug description: I will see week number 13 twise there in this year! so weeks 14-18 are with wrong week number. Screenshot: https://dl.dropboxusercontent.com/u/4435155/Wrong_weeknumber/week.png Ubuntu 14.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evolution-data-server 3.10.4-0ubuntu1.5 Uname: Linux 3.13.0-031300-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 16 18:24:43 2015 ExecutablePath: /usr/lib/evolution/evolution-calendar-factory InstallationDate: Installed on 2013-10-23 (481 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash PATH=(custom, no user) LANG=fi_FI.UTF-8 LD_LIBRARY_PATH=set SourcePackage: evolution-data-server UpgradeStatus: Upgraded to trusty on 2014-06-26 (234 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1422424/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
@Benjaming, http://launchpadlibrarian.net/201756820/nautilus_3.14.2-0ubuntu7_source.changes which is still in the vivid review queue -- 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/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c
@Raphael: Of course we want a consistent behavior in all applications. Since you mention pt_PT, it should be noted that the commit I just made affects pt_BR only. Possibly there is a reason to do the same for pt_PT, but I think it needs to be discussed first. Added a libX11 task to remember it. On 2015-04-01 02:47, Raphael das Neves Calvo wrote: Previous versions and flavors don't need to be fixed, IMHO. Focus on the next release because we already have workarounds for the previous releases. That makes sense for existing users, but wouldn't a better configuration be preferable for new users who install e.g. 14.04? ** Also affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/518056 Title: cedilla appears as accented c (ć instead of ç) when typing 'c Status in central project for keyboard configuration: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Fix Committed Status in libx11 package in Ubuntu: New Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: When typing in a US-international keyboard with dead-keys (or UK-international), typing 'c results in an accented c instead of a cedilla. There is a workaround, which is editing the /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules file and changing the line cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa to cedilla Cedilla gtk20 /usr/share/locale az:ca:co:fr:gv:oc:pt:sq:tr:wa:en (add the 'en' at the end). However, every time some update on this file is applied, one looses the change, and we get back to the accented c. That means having to modify the file again, logout and login. For me this is no problem. But for my brother, mom, dad, etc, it is always something that at least makes me less proud of having convinced them to use Ubuntu, because they don't know what to do each time this happens. I think we really need a configurable keyboard layout, or at least (and that would be very easy), the inclusion of alternate layouts on install that for the dead-key options (as US-deadkey and UK-deakey), alternate layouts as US-deadkey-cedilla. This change is relevant for at least Portuguese and French. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+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 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work
** No longer affects: xserver-xorg-input-synaptics (Ubuntu) ** No longer affects: xserver-xorg-input-synaptics (Ubuntu Trusty) ** No longer affects: xserver-xorg-input-synaptics (Ubuntu Utopic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1414930 Title: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: In Progress Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in systemd source package in Utopic: Confirmed Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+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 1401591] Re: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8
The solution posted by @schlypel worked for me too. I searched nvidia- persitenced with htop. THX for solution! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1401591 Title: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Bug description: I switched to the Nvidia driver not long before I updated the OS to the latest version. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Dec 10 20:45:45 2014 DuplicateSignature: package:nvidia-331:331.113-0ubuntu0.1:subprocess installed post-removal script returned error exit status 8 ErrorMessage: subprocess installed post-removal script returned error exit status 8 InstallationDate: Installed on 2014-12-05 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 331.113-0ubuntu0.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 8 UpgradeStatus: Upgraded to utopic on 2014-12-11 (0 days ago) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1401591/+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 1371220] Re: nautilus crashed with SIGSEGV in nautilus_window_sync_location_widgets()
** Information type changed from Private to Public -- 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/1371220 Title: nautilus crashed with SIGSEGV in nautilus_window_sync_location_widgets() Status in nautilus package in Ubuntu: Confirmed Bug description: seems to have been reported already as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/340222, unfortunately, apport dialog closes after launchpad.net opened in the browser making the examine locally function unavailable... ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 18 19:41:03 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2014-09-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140826) ProcCmdline: nautilus --new-window ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x47b969: cmp%rax,(%rdx) PC (0x0047b969) ok source %rax ok destination (%rdx) (0x0061) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () ?? () 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 g_signal_emit_valist () 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 lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1371220/+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 1439106] [NEW] Xorg crashed with SIGABRT in pixman_region_copy()
Public bug reported: Unexplainable crashes observed on Xorg. Crash occured the last two days. Occured since updates from last week. Unable to use the documented Apport workflow to Report the BUG. Apport workflow was only partielly shown. Tried already sudo apport-cli -c /var/crash/_usr_bin_Xorg.0.crash Annotation 1: In the crash file was the package name printed, but Report a bug said: 2:1.15.1-0ubuntu2.7 does not exist in Ubuntu. Please choose a different package. If you're unsure, please select I don't know Annotation 2: apt-list Xorg printed out the package, but Report a bug said: xorg/trusty-updates,now 1:7.7+1ubuntu8.1 amd64 [installed] does not exist in Ubuntu. Please choose a different package. If you're unsure, please select I don't know ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: compiz-0.9 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/1439106 Title: Xorg crashed with SIGABRT in pixman_region_copy() Status in xorg package in Ubuntu: New Bug description: Unexplainable crashes observed on Xorg. Crash occured the last two days. Occured since updates from last week. Unable to use the documented Apport workflow to Report the BUG. Apport workflow was only partielly shown. Tried already sudo apport-cli -c /var/crash/_usr_bin_Xorg.0.crash Annotation 1: In the crash file was the package name printed, but Report a bug said: 2:1.15.1-0ubuntu2.7 does not exist in Ubuntu. Please choose a different package. If you're unsure, please select I don't know Annotation 2: apt-list Xorg printed out the package, but Report a bug said: xorg/trusty-updates,now 1:7.7+1ubuntu8.1 amd64 [installed] does not exist in Ubuntu. Please choose a different package. If you're unsure, please select I don't know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439106/+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 1212997] Re: USB 3G modem not found in Lubuntu
I only need to add usb_wwan to /etc/modules to make it work. The other modules weren't necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1212997 Title: USB 3G modem not found in Lubuntu Status in network-manager-applet package in Ubuntu: New Bug description: I have a USB 3G modem that works find in Kubuntu. There, I can plug it in and the system automatically detects and sets it up. It appears as a wired network interface and basically works out of the box with no actions needed on my part. However, in Lubuntu, the same modem is not found and even the nm-connection-editor can't find it when I run it manually. The modem is a Huawei E3131: $ lsusb | grep -i huawei Bus 001 Device 006: ID 12d1:1f01 Huawei Technologies Co., Ltd. What should happen is that Lubuntu should find the modem and set it up like in Kubuntu. I have read that others have 3G modems working so the issue might be with just this model of modem. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager-gnome 0.9.8.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri Aug 16 12:11:34 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-08-09 (6 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64+mac (20130808) IpRoute: default via 192.168.2.1 dev eth0 proto static 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.36 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 18ee33eaa-5ef1-4a5f-8995-c38b6bd45b55 802-3-ethernet1376644140 pe 16. elokuuta 2013 12.09.00 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1212997/+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 1022858] Re: Guest session asks for a password after switching users
** Summary changed: - Guest session asks for password when switch back to it + Guest session asks for a password after switching users -- 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/1022858 Title: Guest session asks for a password after switching users Status in lightdm package in Ubuntu: Confirmed Bug description: When I switch back to an already open guest session from my user account, I find that the guest session is locked and it asks for the Guest password (which obviously there isn't because it's a guest session!). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-bin 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Tue Jul 10 09:54:55 2012 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed --- ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True Package: lightdm 1.2.1-0ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35 Tags: precise running-unity Uname: Linux 3.2.0-36-generic x86_64 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/lightdm/+bug/1022858/+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 1427221] Re: i915, broadwell, cannot connect external monitor through Display Port
Vladimír Kriška, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (intel- gfx, not bugzilla) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ? Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger- lists.html . It can take a day for the new e-mail to show up in the respective archive. Thank you for your understanding. ** Package changed: xorg (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed = Triaged -- 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/1427221 Title: i915, broadwell, cannot connect external monitor through Display Port Status in linux package in Ubuntu: Triaged Bug description: Hi, on new laptop (thinkpad t450s) I get error message after connecting external monitor: [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to train DP, aborting And after that, monitor is turned to sleep mode. Interesting thing is, that monitor is detected. I've already reported bug to kernel intel-gfx, so some additional informations can be found there: https://bugzilla.kernel.org/show_bug.cgi?id=94121 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 2 14:17:36 2015 InstallationDate: Installed on 2015-02-26 (3 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-03-10 (19 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Tags: vivid Uname: Linux 3.19.0-10-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2015-03-30 14:23:37,107 DEBUG enabling apt cron job DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.26, 3.19.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2015-03-10 (19 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20BX001YXS Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Tags: vivid ubuntu Uname: Linux 3.19.0-10-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET39WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001YXS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BX001YXS:pvrThinkPadT450s:rvnLENOVO:rn20BX001YXS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX001YXS dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
[Desktop-packages] [Bug 1438740] Re: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply()
It is bug in libwnck and should be fixed in vivid - next ubuntu release. For more info: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1293252 There is ppa with fix... Dmitry, can you backport fix at least to trusty? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1438740 Title: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply() Status in gnome-panel package in Ubuntu: Incomplete Bug description: The game where I observe this is Magicite, however it seems to be the case for other steam games as well. I run gnome-flashback session with compiz on Ubuntu 14.04. When the game starts, the panel crashes and disappears. I have to restart it manually in a shell (it does not automatically respawn). ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu12.2 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 31 17:44:27 2015 ExecutablePath: /usr/bin/gnome-panel ExecutableTimestamp: 1412098123 GsettingsChanges: InstallationDate: Installed on 2014-09-05 (207 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: gnome-panel ProcCwd: /home/ps Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip fuse lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1438740/+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 1201095] Re: gnome-panel crashes after launching steam game (Thomas was alone)
This is bug in libwnck not gnome-panel: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1293252 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1201095 Title: gnome-panel crashes after launching steam game (Thomas was alone) Status in gnome-panel package in Ubuntu: Invalid Bug description: Hello, I encountered a minor problem on Ubuntu 13.04 with Gnome session in fallback mode. After running the game (even without launching steam application), both gnome panels (upper panel and the bottom one) disappear. I had started gnome-panel manually in the terminal and then launched the game. I received a following message: (gnome-panel:3447): Gdk-ERROR **: The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 32189 error_code 8 request_code 62 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Output of apt-cache policy gnome-panel: gnome-panel: Zainstalowana: 1:3.6.2-0ubuntu3 Kandydująca: 1:3.6.2-0ubuntu3 Tabela wersji: *** 1:3.6.2-0ubuntu3 0 500 http://pl.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages 100 /var/lib/dpkg/status and my quick translation: gnome-panel: Version installed: 1:3.6.2-0ubuntu3 Candidate version: 1:3.6.2-0ubuntu3 Table of versions: *** 1:3.6.2-0ubuntu3 0 500 http://pl.archive.ubuntu.com/ubuntu/ raring/universe i386 Packages 100 /var/lib/dpkg/status The game is based on Unity3D engine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1201095/+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 1439006] Re: [FFe] Install Fcitx for Japanese users
On 2015-04-01 13:22, Iain Lane wrote: Presumably the remix can do whatever it wants. Leaving to Ikuya to comment on that. This bug is asking to make the change for *all* Ubuntu users. I think it's quite late in the cycle to do that. Basically the change would only affect new users, just as with Chinese. But you know better than me if it's *too* late. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1439006 Title: [FFe] Install Fcitx for Japanese users Status in im-config package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: According to my proposal [1], Fcitx should be default for Japanese uses on Vivid release cycle. https://lists.ubuntu.com/archives/ubuntu-desktop/2015-March/004645.html Ref: https://bugs.launchpad.net/ubuntu/+source/language- selector/+bug/1430893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1439006/+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 1428328] Re: nvidia-prime needs sddm support
Needs sddm to run commands on login and shut down also investigatae why this isn't just done as systemd units https://lists.ubuntu.com/archives/kubuntu-devel/2015-April/009405.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1428328 Title: nvidia-prime needs sddm support Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Kubuntu 15.04 will use sddm as a default login manager. If we try to install nvidia drivers with nvidia-prime, the second will want to install lightdm as it depends of it. Whats more lightdm will want to install a lot of other packages. What we need: nvidia-prime to support sddm 1. #lsb_release -rd Description:Ubuntu Vivid Vervet (development branch) Release:15.04 2. #apt-cache policy nvidia-prime nvidia-prime: Installed: (none) Candidate: 0.7 Version table: 0.7 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 3. What you expected to happen ? nvidia-prime should work with sddm and do not require lightdm and all its dependencies (unity packges) 4. What happened instead ? nvidia-prime wants to install lightdm as a dependency and a lot of other packages: #sudo apt-get install nvidia-prime Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: adwaita-icon-theme apg avahi-utils bbswitch-dkms cheese-common cups-pk-helper dconf-cli evolution-data-server evolution-data-server-common evolution-data-server-online-accounts geoclue geoclue-ubuntu-geoip gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gdkpixbuf-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomekeyring-1.0 gir1.2-gtk-3.0 gir1.2-ibus-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-pango-1.0 gkbd-capplet gnome-bluetooth gnome-control-center-shared-data gnome-desktop3-data gnome-menus gnome-power-manager gnome-screensaver gnome-session-bin gnome-settings-daemon-schemas gnome-user-guide gnome-user-share gsettings-ubuntu-schemas gstreamer1.0-clutter gvfs-backends humanity-icon-theme hwdata ibus indicator-applet indicator-application indicator-bluetooth indicator-datetime indicator-keyboard indicator-messages indicator-power indicator-session indicator-sound libaccount-plugin-1.0-0 libaccount-plugin-generic-oauth libaccount-plugin-google libaccounts-qt5-1 libappindicator3-1 libcamel-1.2-49 libcdio-cdda1 libcdio-paranoia1 libcheese-gtk23 libcheese7 libclutter-1.0-0 libclutter-1.0-common libclutter-gst-2.0-0 libclutter-gtk-1.0-0 libcogl-common libcogl-pango20 libcogl-path20 libcogl20 libdbusmenu-gtk3-4 libebackend-1.2-7 libebook-1.2-14 libebook-contacts-1.2-0 libecal-1.2-16 libedata-book-1.2-20 libedata-cal-1.2-23 libedataserver-1.2-18 libgdata-common libgdata19 libgee2 libgeocode-glib0 libgnome-bluetooth11 libgnome-desktop-3-10 libgnome-menu-3-0 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgtop2-10 libgtop2-common libgweather-3-6 libgweather-common libido3-0.1-0 libindicator3-7 libinput7 liblightdm-gobject-1-0 libnm-gtk-common libnm-gtk0 liboauth0 libpackagekit-glib2-16 libpanel-applet0 libsignon-extension1 libsignon-glib1 libsignon-plugins-common1 libsignon-qt5-1 libtimezonemap-data libtimezonemap1 libunity-control-center1 libunity-settings-daemon1 liburl-dispatcher1 libwacom-bin libwacom-common libwacom2 libxklavier16 libyelp0 lightdm mousetweaks nautilus-data network-manager-gnome python-notify python3-aptdaemon.pkcompat python3-bs4 python3-cairo python3-html5lib python3-lxml python3-smbc python3-xdg session-migration signon-keyring-extension signon-plugin-oauth2 signon-ui signon-ui-service signon-ui-x11 signond system-config-printer-common system-config-printer-gnome ubuntu-mono ubuntu-system-service ubuntu-touch-sounds unity-control-center unity-control-center-signon unity-greeter unity-settings-daemon yelp yelp-xsl Suggested packages: bumblebee evolution evolution-data-server-dbg apache2.2-bin libapache2-mod-dnssd samba-common ibus-clutter ibus-doc click powerd unity-system-compositor unity-greeter-session-broadcast url-dispatcher nautilus network-manager-openconnect-gnome network-manager-openvpn-gnome network-manager-vpnc-gnome network-manager-pptp-gnome python3-genshi python3-lxml-dbg python-lxml-doc libcanberra-gtk-module lightdm-remote-session-freerdp lightdm-remote-session-uccsconfigure remote-login-service metacity x-window-manager The following NEW packages will be installed: adwaita-icon-theme apg avahi-utils bbswitch-dkms cheese-common cups-pk-helper dconf-cli evolution-data-server evolution-data-server-common evolution-data-server-online-accounts geoclue geoclue-ubuntu-geoip gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gdkpixbuf-2.0
[Desktop-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
Does this also fix the issue where the Files icon in Installed Applications is also pointing to nautilus.desktop instead of the new name? No, I can't confirm that issue, nautilus.desktop has NoDisplay=true and shouldn't show in the dash, not sure why it does for you @Colin, org.gnome.Nautilus.desktop is the new name -- 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/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
Which .desktop file is the one that should be in the launcher? In /usr/share/applications I have three which have Name=Files: nautilus.desktop nautilus-folder-handler.desktop org.gnome.Nautilus.desktop -- 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/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)
Does this also fix the issue where the Files icon in Installed Applications is also pointing to nautilus.desktop instead of the new name? -- 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/1436297 Title: Nautilus launcher icon matching issue (seems due to desktop rename) Status in nautilus package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: STEPS: 1. Boot Latest vivid cd 2. Select Live session or install 3. On the live session or installed system open Nautilus 4. The Nautilus window opens but in the launcher there is now a second window EXPECTED: I expect all nautilus windows to be linked to the original Nautilus launcher ACTUAL: A second nautilus launcher appears and all windows are linked to it instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1436297/+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 1437807] Re: Suspend/resume fails with SNA acceleration on some WMs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- 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/1437807 Title: Suspend/resume fails with SNA acceleration on some WMs Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 15.04 on a new Dell XPS-13 9343 (the 2015 model). It has a i7-5600U CPU and an Intel HD 5500 integrated graphics card. On Unity, suspend/resume appears to work fine. However, with the i3 window manager, it resumes to severe graphics corruption and all text gone from terminals (which also become unresponsive). I can kill i3 using my normal quit key combination, which takes me to an unresponsive and blank purple lightdm login. There are no log messages out of the ordinary. The same issue appears if I use Fluxbox or another lightweight WM, but not if I use Unity or GNOME. If I configure X.org to use UXA acceleration rather than SNA, however, suspend/resume works fine on the affected WMs. (This is why I believe the X server for Intel cards is the culprit). To reproduce: On an XPS-13 (and probably other HD 5500-based machines), start an i3 session and run `pm-suspend`. Resuming the machine should produce the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1437807/+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 1438740] Re: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply()
As I have no memory stick here at the moment I tried some more things: * the crash is reproducible in gnome-flashback compiz * the crash is reproducible in gnome-flashback metacity * the crash is reproducible in unity (when I manually start the gnome-panel) * if I restart the gnome-panel while the game is running, it immediately crashes again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1438740 Title: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply() Status in gnome-panel package in Ubuntu: Incomplete Bug description: The game where I observe this is Magicite, however it seems to be the case for other steam games as well. I run gnome-flashback session with compiz on Ubuntu 14.04. When the game starts, the panel crashes and disappears. I have to restart it manually in a shell (it does not automatically respawn). ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu12.2 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 31 17:44:27 2015 ExecutablePath: /usr/bin/gnome-panel ExecutableTimestamp: 1412098123 GsettingsChanges: InstallationDate: Installed on 2014-09-05 (207 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: gnome-panel ProcCwd: /home/ps Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip fuse lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1438740/+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 1435611] Re: cups-browsed crashed with SIGABRT in __malloc_assert()
Attached is etc/cups/cups-browsed.conf ** Attachment added: etc/cups/cups-browsed.conf https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1435611/+attachment/4362834/+files/cups-browsed.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1435611 Title: cups-browsed crashed with SIGABRT in __malloc_assert() Status in cups-filters package in Ubuntu: Incomplete Bug description: automatic apport ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CupsErrorLog: Date: Mon Mar 23 13:12:54 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-03-10 (13 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUS All Series Papersize: letter ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=a9f12cc3-d420-488e-9b31-319689f5b2c9 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __malloc_assert (assertion=assertion@entry=0x7fd9f3e63560 (unsigned long) (size) = (unsigned long) (nb), file=file@entry=0x7fd9f3e5f282 malloc.c, line=line@entry=3689, function=function@entry=0x7fd9f3e5f60a __func__.11519 _int_malloc) at malloc.c:297 _int_malloc (av=av@entry=0x7fd9f4096c00 main_arena, bytes=bytes@entry=48) at malloc.c:3689 __libc_calloc (n=optimized out, elem_size=optimized out) at malloc.c:3213 ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2 ippAddInteger () from /usr/lib/x86_64-linux-gnu/libcups.so.2 Title: cups-browsed crashed with SIGABRT in __malloc_assert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0317 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x 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.:bvr0317:bd04/23/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1435611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1428972] Re: Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2
I had the very same issue with libsdl1.2-dev under 14.04.2, but since yesterday I can't reproduce it anymore on a clean setup. Fixed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1428972 Title: Unmet dependencies for libcheese-gtk23 and libcheese7 on 14.04.2 Status in unity-control-center package in Ubuntu: Confirmed Bug description: I bumped into this issue while trying to install canonical- certification-client from our PPA [1] ubuntu@201307-13942:~$ sudo apt-get install canonical-certification-client Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: unity-control-center : Depends: libcheese-gtk23 (= 3.4.0) but it is not going to be installed Depends: libcheese7 (= 3.0.1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. However, the version number for these two packages are bigger than the required version number: ubuntu@201307-13942:~$ dpkg -l | grep libcheese-gtk23 ii libcheese-gtk23:amd64 3.10.2-0ubuntu2 amd64tool to take pictures and videos from your webcam - widgets ubuntu@201307-13942:~$ dpkg -l | grep libcheese7 ii libcheese7:amd64 3.10.2-0ubuntu2 amd64tool to take pictures and videos from your webcam - base library ubuntu@201307-13942:~$ I have no clue for how this happens. I thought it was a problem to our PPA (bug 1427524), but I think we're not alone [2] [1] http://ppa.launchpad.net/checkbox-dev/ppa/ubuntu/ [2] http://askubuntu.com/questions/593369/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1428972/+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 1427221] Re: i915, broadwell, cannot connect external monitor through Display Port
Hi Christopher, I tested it with v4.0-rc6-vivid and problem persist. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.0-rc6 ** Changed in: xorg (Ubuntu) Status: Incomplete = 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/1427221 Title: i915, broadwell, cannot connect external monitor through Display Port Status in xorg package in Ubuntu: Confirmed Bug description: Hi, on new laptop (thinkpad t450s) I get error message after connecting external monitor: [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to train DP, aborting And after that, monitor is turned to sleep mode. Interesting thing is, that monitor is detected. I've already reported bug to kernel intel-gfx, so some additional informations can be found there: https://bugzilla.kernel.org/show_bug.cgi?id=94121 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 Uname: Linux 3.19.0-031900-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 2 14:17:36 2015 InstallationDate: Installed on 2015-02-26 (3 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-03-10 (19 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Tags: vivid Uname: Linux 3.19.0-10-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2015-03-30 14:23:37,107 DEBUG enabling apt cron job DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.26, 3.19.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2015-03-10 (19 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20BX001YXS Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Tags: vivid ubuntu Uname: Linux 3.19.0-10-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-30 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET39WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001YXS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BX001YXS:pvrThinkPadT450s:rvnLENOVO:rn20BX001YXS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BX001YXS dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Mar 30 17:09:53 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1439110] [NEW] thunderbird will open but not respond
Public bug reported: Thunderbird opens and dowloads all new emails into the Inbox, but does not respond when trying to open any new email, I now have a backlog of about 70 emails that cannot be opened. I have tried opening in Safe Mode this did not work. I am using Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: fglrx AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2049 F pulseaudio /dev/snd/controlC0: john 2049 F pulseaudio BuildID: 20150223201856 Channel: Unavailable CurrentDesktop: Unity Date: Wed Apr 1 11:23:50 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-anaheim-precise-amd64-20130424-1 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2014-03-09 (388 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130424-09:51 IpRoute: default via 192.168.1.254 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.64 metric 9 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=31.5.0/20150223201856 RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 icedtea-6-plugin 1.5-1ubuntu1 totem-mozilla 3.10.1-1ubuntu4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: True SourcePackage: thunderbird UpgradeStatus: Upgraded to trusty on 2014-08-20 (223 days ago) dmi.bios.date: 06/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 188B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 69.18 dmi.chassis.asset.tag: 5CG410DCVV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.37:bd06/26/2013:svnHewlett-Packard:pnHP255G1NotebookPC:pvr088E1300591600010:rvnHewlett-Packard:rn188B:rvrKBCVersion69.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 255 G1 Notebook PC dmi.product.version: 088E1300591600010 dmi.sys.vendor: Hewlett-Packard ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1439110 Title: thunderbird will open but not respond Status in thunderbird package in Ubuntu: New Bug description: Thunderbird opens and dowloads all new emails into the Inbox, but does not respond when trying to open any new email, I now have a backlog of about 70 emails that cannot be opened. I have tried opening in Safe Mode this did not work. I am using Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:31.5.0+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: fglrx AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2049 F pulseaudio /dev/snd/controlC0: john 2049 F pulseaudio BuildID: 20150223201856 Channel: Unavailable CurrentDesktop: Unity Date: Wed Apr 1 11:23:50 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-anaheim-precise-amd64-20130424-1 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2014-03-09 (388 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130424-09:51 IpRoute: default via 192.168.1.254 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.64 metric 9 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=31.5.0/20150223201856 RelatedPackageVersions: rhythmbox-mozilla 3.0.2-0ubuntu2 icedtea-6-plugin 1.5-1ubuntu1 totem-mozilla 3.10.1-1ubuntu4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked:
[Desktop-packages] [Bug 1439106] Re: Xorg crashed with SIGABRT in pixman_region_copy()
I tried to attach the Xorg crash file. But the Post Comment doesn't submit it. I'm excused but the file size ist ~57 MB. -- 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/1439106 Title: Xorg crashed with SIGABRT in pixman_region_copy() Status in xorg package in Ubuntu: New Bug description: Unexplainable crashes observed on Xorg. Crash occured the last two days. Occured since updates from last week. Unable to use the documented Apport workflow to Report the BUG. Apport workflow was only partielly shown. Tried already sudo apport-cli -c /var/crash/_usr_bin_Xorg.0.crash Annotation 1: In the crash file was the package name printed, but Report a bug said: 2:1.15.1-0ubuntu2.7 does not exist in Ubuntu. Please choose a different package. If you're unsure, please select I don't know Annotation 2: apt-list Xorg printed out the package, but Report a bug said: xorg/trusty-updates,now 1:7.7+1ubuntu8.1 amd64 [installed] does not exist in Ubuntu. Please choose a different package. If you're unsure, please select I don't know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439106/+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 1430093] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()
https://errors.ubuntu.com/problem/94c7537a960f872b3597a51d05110cd42b18bc81 as well ** Description changed: + * Impact: + nautilus sometime segfaults when closing windows with several tabs open + + * Test case: + check https://errors.ubuntu.com/problem/a69a395811666090e103b1a48890e12ef0b433b5 + + or + + try closing nautilus windows with several tabs open, that shouldn't lead + to a segfault + + * regression potential + check for issues on closing and with multiple tabs + + + Close and Crash. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu4 Uname: Linux 4.0.0-04rc3-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Mar 9 22:14:31 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-09-25 (166 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140923) ProcCmdline: nautilus -n SegvAnalysis: - Segfault happened at: 0x7f2392b94f1f g_type_check_instance_is_a+63: testb $0x4,0x16(%rax) - PC (0x7f2392b94f1f) ok - source $0x4 ok - destination 0x16(%rax) (0xe83f8b48fb894866) not located in a known VMA region (needed writable region)! + Segfault happened at: 0x7f2392b94f1f g_type_check_instance_is_a+63: testb $0x4,0x16(%rax) + PC (0x7f2392b94f1f) ok + source $0x4 ok + destination 0x16(%rax) (0xe83f8b48fb894866) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: - g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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 + g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo -- 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/1430093 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_a() Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: * Impact: nautilus sometime segfaults when closing windows with several tabs open * Test case: check https://errors.ubuntu.com/problem/a69a395811666090e103b1a48890e12ef0b433b5 or try closing nautilus windows with several tabs open, that shouldn't lead to a segfault * regression potential check for issues on closing and with multiple tabs Close and Crash. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu4 Uname: Linux 4.0.0-04rc3-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Mar 9 22:14:31 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-09-25 (166 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140923) ProcCmdline: nautilus -n SegvAnalysis: Segfault happened at: 0x7f2392b94f1f g_type_check_instance_is_a+63: testb $0x4,0x16(%rax) PC (0x7f2392b94f1f) ok source $0x4 ok destination 0x16(%rax) (0xe83f8b48fb894866) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1430093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
Re: [Desktop-packages] [Bug 1439006] Re: [FFe] Install Fcitx for Japanese users
On Wed, Apr 01, 2015 at 08:35:53AM -, Gunnar Hjalmarsson wrote: @Iain: Otherwise there would in effect be a regression with respect to the Japanese remix. It has been shipped with fcitix as the default IM framework, making use of the old im-config behavior. The new im-config behavior, which is locale based, breaks that. Presumably the remix can do whatever it wants. This bug is asking to make the change for *all* Ubuntu users. I think it's quite late in the cycle to do that. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1439006 Title: [FFe] Install Fcitx for Japanese users Status in im-config package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: According to my proposal [1], Fcitx should be default for Japanese uses on Vivid release cycle. https://lists.ubuntu.com/archives/ubuntu-desktop/2015-March/004645.html Ref: https://bugs.launchpad.net/ubuntu/+source/language- selector/+bug/1430893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1439006/+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 1439142] Re: failed after install of chrome-stable
*** This bug is a duplicate of bug 860602 *** https://bugs.launchpad.net/bugs/860602 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #860602, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1439142/+attachment/4362887/+files/CoreDump.gz ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1439142/+attachment/4362890/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1439142/+attachment/4362891/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 860602 software-center crashed with SIGSEGV in debListParser::LoadReleaseInfo() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1439142 Title: failed after install of chrome-stable Status in software-center package in Ubuntu: New Bug description: downloaded latest google-chrome-stable_current_amd64.deb open with Ubuntu Software install Ubuntu Software freezes AFTER install is completed Chrome install is apparently successful. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: software-center 13.10-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Apr 1 07:22:19 2015 ExecutablePath: /usr/share/software-center/software-center InstallationDate: Installed on 2015-04-01 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Alpha amd64 (20150225) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center /home/username/Downloads/google-chrome-stable_current_amd64.deb ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1439142/+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 1439186] [NEW] [REGRESSION] Predictor tag fails to be written correctly
Public bug reported: The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF files with compression predictor. It seems the data is correctly saved, but the predictor tag is not, which prevents reading the data correctly again. This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty (release 4.0.3-7ubuntu0.2). I'm attaching an example TIFF file small.tiff for showing the behaviour. It is compressed in LZW without predictor, so it is written/read correctly. However, if you recompress it with this command, the error happens: $ tiffcp -c lzw:2 small.tiff small-c2.tiff Then displaying it in eog shows a completely different image. Tiffinfo indicates a problem with the tags: $ tiffinfo small-c2-bad.tiff | grep Predictor TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Comparing it with a good version of the file (generated with a previous version of libtiff): $ tiffinfo small-c2-good.tiff | grep Predictor Predictor: horizontal differencing 2 (0x2) $ tiffcmp small-c2.tiff small-c2-good.tiff TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Predictor tag appears only in small-c2-good.tiff ** Affects: tiff (Ubuntu) Importance: Undecided Status: New ** Attachment added: Example TIFF file without predictor https://bugs.launchpad.net/bugs/1439186/+attachment/4362958/+files/small.tiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1439186 Title: [REGRESSION] Predictor tag fails to be written correctly Status in tiff package in Ubuntu: New Bug description: The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF files with compression predictor. It seems the data is correctly saved, but the predictor tag is not, which prevents reading the data correctly again. This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty (release 4.0.3-7ubuntu0.2). I'm attaching an example TIFF file small.tiff for showing the behaviour. It is compressed in LZW without predictor, so it is written/read correctly. However, if you recompress it with this command, the error happens: $ tiffcp -c lzw:2 small.tiff small-c2.tiff Then displaying it in eog shows a completely different image. Tiffinfo indicates a problem with the tags: $ tiffinfo small-c2-bad.tiff | grep Predictor TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Comparing it with a good version of the file (generated with a previous version of libtiff): $ tiffinfo small-c2-good.tiff | grep Predictor Predictor: horizontal differencing 2 (0x2) $ tiffcmp small-c2.tiff small-c2-good.tiff TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Predictor tag appears only in small-c2-good.tiff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1439186/+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 1439202] Re: /usr/lib/ibus/ibus-ui-gtk3:11:XKeysymToKeycode:keybinding_manager_bind:panel_keybinding_manager_bind:panel_bind_switch_shortcut:panel_construct
The reports started on march 23 but ibus hadn't change since january, could have to do with the im-config changes around that day? ** Changed in: ibus (Ubuntu) Importance: Undecided = High ** Changed in: ibus (Ubuntu) Status: New = Confirmed ** Changed in: ibus (Ubuntu) Assignee: (unassigned) = Aron Xu (happyaron) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1439202 Title: /usr/lib/ibus/ibus-ui- gtk3:11:XKeysymToKeycode:keybinding_manager_bind:panel_keybinding_manager_bind:panel_bind_switch_shortcut:panel_construct Status in ibus package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ibus. This problem was most recently seen with version 1.5.9-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e11ca2ef905c13162f06fec66b9717ca8861acd3 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1439202/+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 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly
** Attachment added: Example TIFF file with predictor, recorded with latest version of libtiff https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1439186/+attachment/4362959/+files/small-c2-bad.tiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1439186 Title: [REGRESSION] Predictor tag fails to be written correctly Status in tiff package in Ubuntu: New Bug description: The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF files with compression predictor. It seems the data is correctly saved, but the predictor tag is not, which prevents reading the data correctly again. This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty (release 4.0.3-7ubuntu0.2). I'm attaching an example TIFF file small.tiff for showing the behaviour. It is compressed in LZW without predictor, so it is written/read correctly. However, if you recompress it with this command, the error happens: $ tiffcp -c lzw:2 small.tiff small-c2.tiff Then displaying it in eog shows a completely different image. Tiffinfo indicates a problem with the tags: $ tiffinfo small-c2-bad.tiff | grep Predictor TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Comparing it with a good version of the file (generated with a previous version of libtiff): $ tiffinfo small-c2-good.tiff | grep Predictor Predictor: horizontal differencing 2 (0x2) $ tiffcmp small-c2.tiff small-c2-good.tiff TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Predictor tag appears only in small-c2-good.tiff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1439186/+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 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly
** Attachment added: Example TIFF file with predictor, recorded with libtiff without the afromentioned patch https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1439186/+attachment/4362960/+files/small-c2-good.tiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1439186 Title: [REGRESSION] Predictor tag fails to be written correctly Status in tiff package in Ubuntu: New Bug description: The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF files with compression predictor. It seems the data is correctly saved, but the predictor tag is not, which prevents reading the data correctly again. This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty (release 4.0.3-7ubuntu0.2). I'm attaching an example TIFF file small.tiff for showing the behaviour. It is compressed in LZW without predictor, so it is written/read correctly. However, if you recompress it with this command, the error happens: $ tiffcp -c lzw:2 small.tiff small-c2.tiff Then displaying it in eog shows a completely different image. Tiffinfo indicates a problem with the tags: $ tiffinfo small-c2-bad.tiff | grep Predictor TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Comparing it with a good version of the file (generated with a previous version of libtiff): $ tiffinfo small-c2-good.tiff | grep Predictor Predictor: horizontal differencing 2 (0x2) $ tiffcmp small-c2.tiff small-c2-good.tiff TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 (0x2020) encountered. Predictor tag appears only in small-c2-good.tiff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1439186/+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 1438629] Re: Packaged version of UIAutomatorViewer is broken
** Also affects: eclipse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1438629 Title: Packaged version of UIAutomatorViewer is broken Status in androidsdk-tools package in Ubuntu: New Status in eclipse package in Ubuntu: New Bug description: On a fresh Ubuntu 14.04.2 LTS, android-uiautomatorviewer just does not work. Install android-uiautomatorviewer and execute uiautomatorviewer: Exception in thread main java.lang.NoClassDefFoundError: org/eclipse/jface/window/ApplicationWindow at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:412) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482) Caused by: java.lang.ClassNotFoundException: org.eclipse.jface.window.ApplicationWindow at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 14 more The problem is that the wrapper script pass /usr/share/java as parameter for -Djava.ext.dirs, while uiautomatorviewer also depends on eclipse-rcp jars installed in /usr/lib/eclipse/plugins. The patch attached fixes the problem. EDIT: but a better fix is https://bugs.launchpad.net/ubuntu/+source /androidsdk-tools/+bug/1438629/comments/3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/androidsdk-tools/+bug/1438629/+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 1439196] Re: unity-settings-daemon crashed with signal 5 in g_settings_get_value()
*** This bug is a duplicate of bug 1436959 *** https://bugs.launchpad.net/bugs/1436959 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1436959, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1439196/+attachment/4362981/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1439196/+attachment/4362983/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1439196/+attachment/4362985/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1439196/+attachment/4362986/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1439196/+attachment/4362987/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1439196/+attachment/4362988/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1439196/+attachment/4362989/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1436959 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1439196 Title: unity-settings-daemon crashed with signal 5 in g_settings_get_value() Status in unity-settings-daemon package in Ubuntu: New Bug description: This happended when starting computer ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-settings-daemon 15.04.1+15.04.20150324.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Apr 1 09:15:55 2015 ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon InstallationDate: Installed on 2015-03-28 (4 days ago) InstallationMedia: Ubuntu-Desktop-Next 15.04 Vivid Vervet - Alpha amd64 (20150308) ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR=set Signal: 5 SourcePackage: unity-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/unity-settings-daemon-1.0/libkeyboard.so SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: unity-settings-daemon crashed with signal 5 in g_settings_get_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1439196/+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 1439191] [NEW] [vivid regression] X.org fails to start on i386 cirrus
Public bug reported: This was spotted by systemd's tests (which involve lightdm) starting to fail. Cirrus cards (as provided by QEMU) still worked fine until at least 2015-03-11 (https://jenkins.qa.ubuntu.com/job/vivid-adt- systemd/119/), but started to fail now. Start a current i386 vivid image in QEMU with -vga cirrus (which is the default with trusty's QEMU, which is how we noticed), install lightdm, then X.org will fail with Fatal server error: [ 117.236] (EE) failed to create screen resources(EE) The apport collected info is from that VM, it should have all the logs. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-cirrus 1:1.5.2-2ubuntu1 ProcVersionSignature: User Name 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Apr 1 15:06:28 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=f2ba9998-2ff5-4189-85c4-ed50827dbd8e ro console=ttyS0 vmalloc=512M Renderer: Software SourcePackage: xserver-xorg-video-cirrus UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Apr 1 15:00:49 2015 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output VGA-0 xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: modeset ** Affects: xserver-xorg-video-cirrus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 ubuntu vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1439191 Title: [vivid regression] X.org fails to start on i386 cirrus Status in xserver-xorg-video-cirrus package in Ubuntu: Confirmed Bug description: This was spotted by systemd's tests (which involve lightdm) starting to fail. Cirrus cards (as provided by QEMU) still worked fine until at least 2015-03-11 (https://jenkins.qa.ubuntu.com/job/vivid-adt- systemd/119/), but started to fail now. Start a current i386 vivid image in QEMU with -vga cirrus (which is the default with trusty's QEMU, which is how we noticed), install lightdm, then X.org will fail with Fatal server error: [ 117.236] (EE) failed to create screen resources(EE) The apport collected info is from that VM, it should have all the logs. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-cirrus 1:1.5.2-2ubuntu1 ProcVersionSignature: User Name 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Apr 1 15:06:28 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set
[Desktop-packages] [Bug 1439191] Re: [vivid regression] X.org fails to start on i386 cirrus
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-cirrus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1439191 Title: [vivid regression] X.org fails to start on i386 cirrus Status in xserver-xorg-video-cirrus package in Ubuntu: Confirmed Bug description: This was spotted by systemd's tests (which involve lightdm) starting to fail. Cirrus cards (as provided by QEMU) still worked fine until at least 2015-03-11 (https://jenkins.qa.ubuntu.com/job/vivid-adt- systemd/119/), but started to fail now. Start a current i386 vivid image in QEMU with -vga cirrus (which is the default with trusty's QEMU, which is how we noticed), install lightdm, then X.org will fail with Fatal server error: [ 117.236] (EE) failed to create screen resources(EE) The apport collected info is from that VM, it should have all the logs. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-cirrus 1:1.5.2-2ubuntu1 ProcVersionSignature: User Name 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Apr 1 15:06:28 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=f2ba9998-2ff5-4189-85c4-ed50827dbd8e ro console=ttyS0 vmalloc=512M Renderer: Software SourcePackage: xserver-xorg-video-cirrus UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.7.5-20150306_163512-brownie dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-utopic dmi.modalias: dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-utopic dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Apr 1 15:00:49 2015 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output VGA-0 xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-cirrus/+bug/1439191/+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 1342031] Re: Rename QML modules to follow qml-module-foo naming
** Branch unlinked: lp:~online-accounts/accounts-qml-module/packaging -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qtlocation-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1342031 Title: Rename QML modules to follow qml-module-foo naming Status in accounts-qml-module package in Ubuntu: Fix Released Status in address-book-app package in Ubuntu: New Status in bacon2d package in Ubuntu: Triaged Status in clickmanager-plugin package in Ubuntu: New Status in content-hub package in Ubuntu: New Status in cordova-ubuntu package in Ubuntu: New Status in dee-qt package in Ubuntu: New Status in gsettings-qt package in Ubuntu: New Status in history-service package in Ubuntu: New Status in libhud-qt package in Ubuntu: Won't Fix Status in libqofono package in Ubuntu: New Status in libusermetrics package in Ubuntu: New Status in mediascanner2 package in Ubuntu: New Status in poppler-qml-plugin package in Ubuntu: New Status in qml-box2d package in Ubuntu: New Status in qml-friends package in Ubuntu: New Status in qt3d-opensource-src package in Ubuntu: Fix Released Status in qtconnectivity-opensource-src package in Ubuntu: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtfeedback-opensource-src package in Ubuntu: Fix Released Status in qtgrilo package in Ubuntu: New Status in qtlocation-opensource-src package in Ubuntu: Fix Released Status in qtmultimedia-opensource-src package in Ubuntu: Fix Released Status in qtpim-opensource-src package in Ubuntu: Fix Released Status in qtquickcontrols-opensource-src package in Ubuntu: Fix Released Status in qtsensors-opensource-src package in Ubuntu: Fix Released Status in qtsystems-opensource-src package in Ubuntu: Fix Released Status in reminders-app package in Ubuntu: New Status in solid package in Ubuntu: New Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: Triaged Status in thumbnailer package in Ubuntu: New Status in u1db-qt package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: Triaged Status in ubuntu-keyboard package in Ubuntu: New Status in ubuntu-settings-components package in Ubuntu: New Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Status in ubuntu-ui-extras package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in ubuntuone-credentials package in Ubuntu: New Status in unity-action-api package in Ubuntu: Triaged Status in unity-notifications package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The package names of QML modules should be of the format qml- module-{$modulename}[version], a transition that was started during Qt 5.3 preparation in Ubuntu. For example this could be qml-module- qtquick-localstorage or qml-module-qtsysteminfo for non versioned modules, and qml-module-ubuntu-webthing0.3 for versioned/co- installable modules. Further details in Debian e-mail: http://lists.alioth.debian.org/pipermail/pkg-kde- talk/2014-March/001889.html For Ubuntu, transitional packages should be put in place for smooth distribution upgrades, since we're shipping with the old names in previous Ubuntus. An example of that is at http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31 - in other words: - Make the old package a transitional oldlibs package that depends on the new package - Add Breaks/Replaces to the new package for the old non-transitional packages (be careful about the version number specification) - Keep Multi-Arch: same and Architecture: any for the transitional package - Write QML module instead of QML plugin - Rename also the *.install files --- One more example on naming: For example, the test (qtdeclarative5-test-plugin) in the old qtdeclarative5-style package naming became qttest (qml-module- qttest) in the new naming since the path is actually under /usr/lib/*/qt5/qml/QtTest/ qml-module-qtquick-xmllistmodel has path /usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have more than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be qml-module-ubuntu-connectivity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+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 1438740] Re: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply()
I can confirm that the ppa in 1293252 fixes the crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1438740 Title: gnome-panel crashes when starting Unity 3D engine steam game - signal 5 in _XReply() Status in gnome-panel package in Ubuntu: Incomplete Bug description: The game where I observe this is Magicite, however it seems to be the case for other steam games as well. I run gnome-flashback session with compiz on Ubuntu 14.04. When the game starts, the panel crashes and disappears. I have to restart it manually in a shell (it does not automatically respawn). ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu12.2 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 31 17:44:27 2015 ExecutablePath: /usr/bin/gnome-panel ExecutableTimestamp: 1412098123 GsettingsChanges: InstallationDate: Installed on 2014-09-05 (207 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: gnome-panel ProcCwd: /home/ps Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip fuse lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1438740/+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 1439202] [NEW] /usr/lib/ibus/ibus-ui-gtk3:11:XKeysymToKeycode:keybinding_manager_bind:panel_keybinding_manager_bind:panel_bind_switch_shortcut:panel_construct
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding ibus. This problem was most recently seen with version 1.5.9-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e11ca2ef905c13162f06fec66b9717ca8861acd3 contains more details. ** Affects: ibus (Ubuntu) Importance: High Assignee: Aron Xu (happyaron) Status: Confirmed ** Tags: vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1439202 Title: /usr/lib/ibus/ibus-ui- gtk3:11:XKeysymToKeycode:keybinding_manager_bind:panel_keybinding_manager_bind:panel_bind_switch_shortcut:panel_construct Status in ibus package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ibus. This problem was most recently seen with version 1.5.9-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e11ca2ef905c13162f06fec66b9717ca8861acd3 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1439202/+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 1431998] Re: stopping network-manager takes several seconds
*** This bug is a duplicate of bug 1438612 *** https://bugs.launchpad.net/bugs/1438612 This is most likely a duplicate of bug 1438612. If you still get this problem in latest vivid, can you please yell here and provide the journal output as in comment #3? I'll unduplicate it then. Thanks! ** This bug has been marked a duplicate of bug 1438612 remote file systems hang on shutdown, D-BUS stops too early -- 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/1431998 Title: stopping network-manager takes several seconds Status in network-manager package in Ubuntu: Incomplete Bug description: kubuntu 15.04 - when rebooting I'm getting on tty1 a stop job is running for network manager takes 10-15 secs to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431998/+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 1293252] Re: gnome-panel crashed with signal 5 in _XReply()
** Also affects: libwnck3 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: libwnck3 (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: libwnck3 (Ubuntu Vivid) Importance: Medium Status: Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1293252 Title: gnome-panel crashed with signal 5 in _XReply() Status in libwnck3 package in Ubuntu: Fix Released Status in libwnck3 source package in Trusty: Confirmed Status in libwnck3 source package in Utopic: Confirmed Status in libwnck3 source package in Vivid: Fix Released Bug description: [Impact] * Games using the Unity engine (like KSP) cause gnome-panel to crash, making things like flashback unusable. [Test Case] * Run gnome-panel (like in gnome flashback). * Launch Kerbal Space Program. Not sure whether there's a simpler test case for those without KSP. [Regression Potential] * The patch for the bug suggests the possibility of weirdly colored icons where crashes used to occur. [Other Info] * libwnck3 (3.14.0-1) allows gnome-panel to continue running in 14.10. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 16 23:53:20 2014 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: InstallationDate: Installed on 2014-02-28 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) ProcCmdline: gnome-panel ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1293252/+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