[Desktop-packages] [Bug 1246203] Re: Mouse pointer does not appear
** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246203 Title: Mouse pointer does not appear Status in “xserver-xorg-input-evdev” package in Ubuntu: Fix Released Bug description: It's a weird thing: I have an Apple magic mouse connected via bluetooth to my Dell XPS 13 laptop. When gnome shell starts, the mouse pointer is is not shown on the screen... however if a move the mouse, the pointer it is still not shown but it actually moves... if fact if I keep moving the mouse towards NW (that is where the top left corner of the screen is) the gnome shell overview mode is activated. In order to make my mouse pointer visible, I have to touch the touchpad. From that moment on, the mouse pointer will be visible. It's a minor thing but it can be annoying especially if you disable the touchpad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 30 07:53:25 2013 InstallationDate: Installed on 2013-05-27 (155 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. XPS L322X MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2013-10-17 (12 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: C8:F7:33:83:A7:0B ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:76231 acl:3866 sco:0 events:283 errors:0 TX bytes:3411 acl:92 sco:0 commands:98 errors:0 mtime.conffile..etc.bluetooth.input.conf: 2013-07-26T11:37:53.325690 mtime.conffile..etc.bluetooth.main.conf: 2013-07-25T15:50:55.459853 --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistUpgraded: 2013-10-17 21:42:13,870 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu InstallationDate: Installed on 2013-05-27 (156 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. XPS L322X MarkForUpload: True Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=4a7e3b74-1859-4197-974a-f319d6af8ee6 ro reboot=efi quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Tags: saucy ubuntu Uname: Linux 3.8.0-29-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-17 (13 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 091F4Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn091F4Y:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 31 08:16:44 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log
[Desktop-packages] [Bug 1249983] Re: Firefox crashed with SIGSEGV
Following this incident, I decided to close this post, Firefox has changed since that day. Sincerely, ~~ Neptunia ~~ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1249983 Title: Firefox crashed with SIGSEGV Status in “firefox” package in Ubuntu: Invalid Bug description: Firefox crashed with SIGSEGV Firefox has crashed when I used FireFTP 2.0.16. This report file is very long... ProblemType: Crash Architecture: amd64 Date: Sun Nov 10 10:22:19 2013 DistroRelease: Ubuntu 13.04 ExecutablePath: /usr/lib/firefox/firefox ExecutableTimestamp: 1382964635 ProcCmdline: /usr/lib/firefox/firefox ProcCwd: /home/neptune2 !!Linux Distribution !!-- Ubuntu 13.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION=ubuntu 13.04 NAME=Ubuntu ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu 13.04 HOME_URL=http://www.ubuntu.com/; SUPPORT_URL=http://help.ubuntu.com/; BUG_REPORT_URL=http://bugs.launchpad.net/ubuntu/; !!DMI Information !!--- Manufacturer: ASUSTeK Computer Inc. Product Name: K73BR Product Version: 1.0 !!Kernel Information !!-- Kernel release:3.8.0-32-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes MarkForUpload: True Package: firefox 25.0+build3-0ubuntu0.13.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1249983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1250759] Re: gnome-control-center sound-nua does not change from internal speakers to external soundcard automatically
David, I am thankful that it does. It should be the default behaviour IMO. -- 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/1250759 Title: gnome-control-center sound-nua does not change from internal speakers to external soundcard automatically Status in “gnome-control-center” package in Ubuntu: New Bug description: The sound is routed through the external soundcard when plugged in, but gnome-control-center sound-nua shows the internal speakers to be active. This means controlling the sound will control the internal speakers and thus have no effect on external sound card. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 13 09:49:33 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-08-27 (77 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-17 (26 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1250759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 471646] Re: [K8M800]with kernel 2.6.31-14-generic my X server crashes during KDE 4.3.2 startup, _mesa_reference_renderbuffer() assertion
** Changed in: debian Status: Incomplete = Fix Released -- 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/471646 Title: [K8M800]with kernel 2.6.31-14-generic my X server crashes during KDE 4.3.2 startup, _mesa_reference_renderbuffer() assertion Status in openchrome: New Status in “linux” package in Ubuntu: Fix Released Status in “mesa” package in Ubuntu: Invalid Status in “xserver-xorg-video-openchrome” package in Ubuntu: Triaged Status in Debian GNU/Linux: Fix Released Status in Gentoo Linux: New Bug description: I just upgraded my Jaunty machine running Linux 2.6.28-16-generic to Karmic running Linux 2.6.31-14-generic, and noticed that KDE crashes back to the KDM login screen during startup. I can run Fluxbox just fine, and KDE works if I boot into Linux 2.6.28-16-generic. I can also startx remotely over Xephyr/SSH. Locally, however, I get the following error in kdm.log (and output during startx): =[ CUT ]= X.Org X Server 1.6.4 Release Date: 2009-9-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-23-server i686 Ubuntu Current Operating System: Linux phoenix 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 Kernel command line: root=UUID=c29b60cc-e6ef-450c-b3c5-ea761c6e3416 ro single Build Date: 26 October 2009 05:15:02PM xorg-server 2:1.6.4-2ubuntu4 (buildd@) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Mon Nov 2 14:39:52 2009 (==) Using config file: /etc/X11/xorg.conf Fulfilled via DRI at 20976640 Freed 20976640 (pool 2) X: main/renderbuffer.c:2159: _mesa_reference_renderbuffer: Assertion `oldRb-Magic == 0xaabbccdd' failed. xinit: connection to X server lost. =[ CUT ]= I'm using a VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] (rev 01) video chipset with the xserver-xorg-video-openchrome driver, and the crash occurs whether I use an xorg.conf or not. The xorg.conf, if used, is =[ CUT ]= Section Device Identifier Configured Video Device Option UseFBDev true EndSection Section Monitor Identifier Configured Monitor Option DPMS HorizSync 31.5-65.2 # 31.5-37.9 EndSection Section Screen Identifier Default Screen Monitor Configured Monitor Device Configured Video Device DefaultDepth24 SubSection Display Depth24 Modes1280x1024 EndSubSection EndSection =[ CUT ]= I'd appreciate any help with this matter, and advice about other information that I should provide. Thanks! ProblemType: Bug Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer', '/dev/sequencer2'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'V8237'/'VIA 8237 with ALC655 at 0xd400, irq 22' Mixer name : 'Realtek ALC655 rev 0' Components : 'AC97a:414c4760' Controls : 48 Simple ctrls : 29 Date: Mon Nov 2 15:29:22 2009 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=f4ed7091-30d8-4c93-9e4b-e7ae7eb77d34 Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=c29b60cc-e6ef-450c-b3c5-ea761c6e3416 ro quiet splash ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 RfKill: SourcePackage: linux Uname: Linux 2.6.31-14-generic i686 WpaSupplicantLog: XsessionErrors: (process:3009): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion `display != NULL' failed (unknown:3009): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed dmi.bios.date: 12/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: K8M800-8237 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/29/2006:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/openchrome/+bug/471646/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 931986] Re: Firefox crashes upon using any addon in 10.0 and 10.0.1
This has long been fixed now in subsequent releases, hence can't be replicated any more. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/931986 Title: Firefox crashes upon using any addon in 10.0 and 10.0.1 Status in “firefox” package in Ubuntu: Invalid Bug description: Symptoms absolutely similar to that of reported herein - https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/931637 Yet created this bug to report further details that I found using ubuntu-bug and firefox-dbg to assist in quick resolution. If found similar to the one referred above then this may be marked as duplicate. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 10.0.1+build1-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21 Uname: Linux 2.6.32-38-generic x86_64 AddonCompatCheckDisabled: False AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:223: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:223: no soundcards found... BuildID: 20120209215013 Channel: release Date: Tue Feb 14 15:56:48 2012 EtcFirefoxSyspref: Cannot parse /etc/firefox/syspref.js - [Errno 2] No such file or directory: '/etc/firefox/syspref.js' ForcedLayersAccel: False IncompatibleExtensions: FireDiff - ID=fired...@johnjbarton.com, Version=1.1.4, minVersion=3.6, maxVersion=7.*, Location=app-profile, Type=extension, Active=Yes Firefinder for Firebug - ID=firefin...@robertnyman.com, Version=1.04, minVersion=3.5, maxVersion=6.*, Location=app-profile, Type=extension, Active=Yes selectbug - ID=select...@getfirebug.com, Version=0.1a2, minVersion=1.9.0.*, maxVersion=2.0.0.*, Location=app-profile, Type=extension, Active=Yes Awesome screenshot: Capture and Annotate - ID=jid0-GXjLLfbCoAx0LcltEdFrEkQdQPI@jetpack, Version=2.3.6, minVersion=8.0, maxVersion=9.*, Location=app-profile, Type=extension, Active=Yes InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) PciMultimedia: ProcEnviron: LANG=en_IN SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=10.0.1/20120209215013 RunningIncompatibleAddons: True SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/931986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270747] [NEW] No more passphare dialog on SSH
Public bug reported: Previously when I opened a terminal and made an SSH connection I would get pop-up dialog asking to unlock the public key with the passphrase. Well, the dialog is no longer appearing. I can unlock the public key in the terminal, but the unlocked key is not saved in the keyring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 10:47:48 2014 InstallationDate: Installed on 2013-09-10 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-23 (88 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1270747 Title: No more passphare dialog on SSH Status in “gnome-keyring” package in Ubuntu: New Bug description: Previously when I opened a terminal and made an SSH connection I would get pop-up dialog asking to unlock the public key with the passphrase. Well, the dialog is no longer appearing. I can unlock the public key in the terminal, but the unlocked key is not saved in the keyring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 10:47:48 2014 InstallationDate: Installed on 2013-09-10 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-23 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1270747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270747] Re: No more passphare dialog on SSH
in /var/log/auth.log I see following messages gnome-keyring-daemon[2314]: couldn't set environment variable in session: Setenv interface is only available during the Initialization phase -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1270747 Title: No more passphare dialog on SSH Status in “gnome-keyring” package in Ubuntu: New Bug description: Previously when I opened a terminal and made an SSH connection I would get pop-up dialog asking to unlock the public key with the passphrase. Well, the dialog is no longer appearing. I can unlock the public key in the terminal, but the unlocked key is not saved in the keyring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 10:47:48 2014 InstallationDate: Installed on 2013-09-10 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-23 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1270747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 206884]
Hi Athira, You need to change (off) in [1] to Universal. To see the change, you could just build toolkit/locales/ with `mach build toolkit/locales/` and `mach run` to see the changes. Good Luck! [1]: http://mxr.mozilla.org/mozilla-central/source/toolkit/locales/en- US/chrome/global/charsetMenu.dtd#10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/206884 Title: fuzzy/confusing firefox View - Character encoding menu semantics Status in The Mozilla Firefox Browser: Confirmed Status in The Great Mass of Obsolete Junk: Won't Fix Status in “firefox” package in Ubuntu: Triaged Bug description: Please note that I am not the reporter of this bug any longer. Alexander Sack is. He changed the title to his own understanding. I personnally understand View - Character encoding perfectly. What I say is that FF does not always display ISO8859-1 by default. André. I have seen this since long with both Firefox 2.x and 3.0b3. Rem: Please note that I don't say that Firefox always uses the wrong encoding. Please read my followup to see how to reproduce the problem. I display, for example, http://atilf.atilf.fr/tlf.htm Its header is HEAD TITLE Le Trésor de la Langue Française Informatisé /TITLE link rel=stylesheet type=text/css href=atilf.css /HEAD Hence, its encoding should be ISO8859-1 by default as it has always been. As the uploaded attachment shows Firefox displays it using UTF-8. In Edit|Preferences|Content|Font Colors|Default font|Advanced|Character Encoding there's an option named Default character encoding documented as follows The character encoding selected here will be used to display pages that do not specify which encoding to use. What's the use of this setting if the default must ALWAYS be ISO8859-1? Otherwise said, what would be the definition of a changing default? It can only cause people to _produce_ the error I describe. Hence, produce confusion. I saw people say that the wrong behavior I describe is caused by a wrong setting. There should obviously be no user setting for a necessary default. How could the heck a user know what default to set in his browser before being able to read a page if the only place it can be said is in that page he could only read by setting the correct default ;-) And this option was left to ISO8859-1 in my browser, of course. Search www.w3.org/TR/html401/charset.html for default and you will learn that a HTML document character code that should obviously be specified within the document is designed to be specified in the HTTP header (without saying BTW how it is specified when FTP is used) with ISO8859-1 as the default. Note that this blunder attributed to HTTP servers accused of not being able to detect the character code of files they store or of being misconfigured has been circumvented by introducing a META directive able to provide -- from the HTML document itself -- HTTP header data and hence the character code. But note that this is done without concluding that ISO8859-1 is the default code of META too, and hence of the document, without regard to the following question. Question : how the heck could a HTML user agent that ignores the default character set work any better than my posting this if you and I didn't know that we have to use ASCII? Answer : no better than the page display I show in my attachment. And finally, note that if the reliability of the expected result of a standard lies in this phrase : By combining these mechanisms, an author can greatly improve the chances that, when the user retrieves a resource, the user agent will recognize the character encoding. the conclusion is : OK, OK, that was only my bad luck again, it's a random game, bug dismissed, Firefox within said specs, I have to try again. Or should we try to see why Firefox didn't display ISO8859-1? I've see browsers do that for years. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/206884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 206884]
(In reply to Masatoshi Kimura [:emk] from comment #14) No, no, not at all. Universal is going to be killed. I think this bug is obsolete due to recent massive changes to Character Encoding menu. In that case, I am letting someone else take over this :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/206884 Title: fuzzy/confusing firefox View - Character encoding menu semantics Status in The Mozilla Firefox Browser: Confirmed Status in The Great Mass of Obsolete Junk: Won't Fix Status in “firefox” package in Ubuntu: Triaged Bug description: Please note that I am not the reporter of this bug any longer. Alexander Sack is. He changed the title to his own understanding. I personnally understand View - Character encoding perfectly. What I say is that FF does not always display ISO8859-1 by default. André. I have seen this since long with both Firefox 2.x and 3.0b3. Rem: Please note that I don't say that Firefox always uses the wrong encoding. Please read my followup to see how to reproduce the problem. I display, for example, http://atilf.atilf.fr/tlf.htm Its header is HEAD TITLE Le Trésor de la Langue Française Informatisé /TITLE link rel=stylesheet type=text/css href=atilf.css /HEAD Hence, its encoding should be ISO8859-1 by default as it has always been. As the uploaded attachment shows Firefox displays it using UTF-8. In Edit|Preferences|Content|Font Colors|Default font|Advanced|Character Encoding there's an option named Default character encoding documented as follows The character encoding selected here will be used to display pages that do not specify which encoding to use. What's the use of this setting if the default must ALWAYS be ISO8859-1? Otherwise said, what would be the definition of a changing default? It can only cause people to _produce_ the error I describe. Hence, produce confusion. I saw people say that the wrong behavior I describe is caused by a wrong setting. There should obviously be no user setting for a necessary default. How could the heck a user know what default to set in his browser before being able to read a page if the only place it can be said is in that page he could only read by setting the correct default ;-) And this option was left to ISO8859-1 in my browser, of course. Search www.w3.org/TR/html401/charset.html for default and you will learn that a HTML document character code that should obviously be specified within the document is designed to be specified in the HTTP header (without saying BTW how it is specified when FTP is used) with ISO8859-1 as the default. Note that this blunder attributed to HTTP servers accused of not being able to detect the character code of files they store or of being misconfigured has been circumvented by introducing a META directive able to provide -- from the HTML document itself -- HTTP header data and hence the character code. But note that this is done without concluding that ISO8859-1 is the default code of META too, and hence of the document, without regard to the following question. Question : how the heck could a HTML user agent that ignores the default character set work any better than my posting this if you and I didn't know that we have to use ASCII? Answer : no better than the page display I show in my attachment. And finally, note that if the reliability of the expected result of a standard lies in this phrase : By combining these mechanisms, an author can greatly improve the chances that, when the user retrieves a resource, the user agent will recognize the character encoding. the conclusion is : OK, OK, that was only my bad luck again, it's a random game, bug dismissed, Firefox within said specs, I have to try again. Or should we try to see why Firefox didn't display ISO8859-1? I've see browsers do that for years. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/206884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 206884]
No, no, not at all. Universal is going to be killed. I think this bug is obsolete due to recent massive changes to Character Encoding menu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/206884 Title: fuzzy/confusing firefox View - Character encoding menu semantics Status in The Mozilla Firefox Browser: Confirmed Status in The Great Mass of Obsolete Junk: Won't Fix Status in “firefox” package in Ubuntu: Triaged Bug description: Please note that I am not the reporter of this bug any longer. Alexander Sack is. He changed the title to his own understanding. I personnally understand View - Character encoding perfectly. What I say is that FF does not always display ISO8859-1 by default. André. I have seen this since long with both Firefox 2.x and 3.0b3. Rem: Please note that I don't say that Firefox always uses the wrong encoding. Please read my followup to see how to reproduce the problem. I display, for example, http://atilf.atilf.fr/tlf.htm Its header is HEAD TITLE Le Trésor de la Langue Française Informatisé /TITLE link rel=stylesheet type=text/css href=atilf.css /HEAD Hence, its encoding should be ISO8859-1 by default as it has always been. As the uploaded attachment shows Firefox displays it using UTF-8. In Edit|Preferences|Content|Font Colors|Default font|Advanced|Character Encoding there's an option named Default character encoding documented as follows The character encoding selected here will be used to display pages that do not specify which encoding to use. What's the use of this setting if the default must ALWAYS be ISO8859-1? Otherwise said, what would be the definition of a changing default? It can only cause people to _produce_ the error I describe. Hence, produce confusion. I saw people say that the wrong behavior I describe is caused by a wrong setting. There should obviously be no user setting for a necessary default. How could the heck a user know what default to set in his browser before being able to read a page if the only place it can be said is in that page he could only read by setting the correct default ;-) And this option was left to ISO8859-1 in my browser, of course. Search www.w3.org/TR/html401/charset.html for default and you will learn that a HTML document character code that should obviously be specified within the document is designed to be specified in the HTTP header (without saying BTW how it is specified when FTP is used) with ISO8859-1 as the default. Note that this blunder attributed to HTTP servers accused of not being able to detect the character code of files they store or of being misconfigured has been circumvented by introducing a META directive able to provide -- from the HTML document itself -- HTTP header data and hence the character code. But note that this is done without concluding that ISO8859-1 is the default code of META too, and hence of the document, without regard to the following question. Question : how the heck could a HTML user agent that ignores the default character set work any better than my posting this if you and I didn't know that we have to use ASCII? Answer : no better than the page display I show in my attachment. And finally, note that if the reliability of the expected result of a standard lies in this phrase : By combining these mechanisms, an author can greatly improve the chances that, when the user retrieves a resource, the user agent will recognize the character encoding. the conclusion is : OK, OK, that was only my bad luck again, it's a random game, bug dismissed, Firefox within said specs, I have to try again. Or should we try to see why Firefox didn't display ISO8859-1? I've see browsers do that for years. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/206884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270747] Re: No more passphare dialog on SSH
Correction: $ ssh-add does add it to the keyring. I just had to add my current key by name. $ ssh-add id_rsa.1 Still no dialog, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1270747 Title: No more passphare dialog on SSH Status in “gnome-keyring” package in Ubuntu: New Bug description: Previously when I opened a terminal and made an SSH connection I would get pop-up dialog asking to unlock the public key with the passphrase. Well, the dialog is no longer appearing. I can unlock the public key in the terminal, but the unlocked key is not saved in the keyring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 10:47:48 2014 InstallationDate: Installed on 2013-09-10 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-23 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1270747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
Is this bug really fixed? I'm using Ubuntu 13.10 and I still cannot connect to my company network which is WPA2 enterprise PEAP without CA certificate. -- 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/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Triaged Status in Gentoo Linux: Fix Released Status in “network-manager” package in openSUSE: Confirmed Bug description: === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080635] Re: Evolution tries to download non existant image
This problem still exists in 12.04.4. I have added a screenshot. When this happens I am unable to close evolution and I have to use evolution --force-shutdown from the command line to close evolution! It would have been better if evolution would time out images it cannot load. ** Attachment added: Screenshot from 2014-01-20 10:32:34 - 2.png https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1080635/+attachment/3952656/+files/Screenshot%20from%202014-01-20%2010%3A32%3A34%20-%202.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1080635 Title: Evolution tries to download non existant image Status in “evolution” package in Ubuntu: New Bug description: If you open an email with an image which doesn't exist it does not time out and keeps on trying to download this image. I cannot open any other emails with the preview window. The only way to view other emails is by opening them in a new window. I am running a dovecot IMAP server. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Mon Nov 19 11:38:35 2012 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2011-10-13 (402 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1080635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270772] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1033533 *** https://bugs.launchpad.net/bugs/1033533 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 #1033533, 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/1270772/+attachment/3952659/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1270772/+attachment/3952662/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1270772/+attachment/3952674/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1270772/+attachment/3952676/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1270772/+attachment/3952677/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1270772/+attachment/3952678/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1270772/+attachment/3952679/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1033533 Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering ** 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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1270772 Title: Xorg crashed with SIGABRT Status in “xorg-server” package in Ubuntu: New Bug description: I was doing a dist-upgrade, and then xorg/nouveau crashed in the middle of it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.14.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jan 20 09:38:42 2014 DistUpgraded: 2013-05-07 09:32:51,766 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.2, 3.13.0-2-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-3-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-4-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:2670] InstallationDate: Installed on 2012-10-07 (469 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-4-generic root=UUID=980689ca-e7d9-4a99-8230-33b8b6e917cd ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to trusty on 2013-05-07 (258 days ago) UserGroups: dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1033533] Re: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering
** Tags added: trusty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1033533
Title:
Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with
SW rendering
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
Triaged
Status in “xserver-xorg-video-nouveau” source package in Quantal:
Triaged
Status in “xserver-xorg-video-nouveau” source package in Raring:
Triaged
Bug description:
[Errors Bucket]
https://errors.ubuntu.com/bucket/?id=/usr/bin/Xorg:6:memcpy:exaMemcpyBox:exaCopyDirty:exaCopyDirtyToSys:exaPrepareAccessReg_mixed
Crash doing memcpy in EXA on nouveau, with software rendering
activated.
#8 signal handler called
No symbol table info available.
#9 __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:72
No locals.
#10 0x7f570e63684e in memcpy (__len=23, __src=0x0, __dest=0x7f5713877100)
at /usr/include/x86_64-linux-gnu/bits/string3.h:52
No locals.
#11 exaMemcpyBox (pbox=pbox@entry=0x7fffef000de0, src=0x0, src_pitch=64,
dst=0x7f5713877100 , dst_pitch=24, pPixmap=error reading variable: Unhandled
dwarf expression opcode 0xfa) at ../../exa/exa_migration_classic.c:59
i = 16
cpp = optimized out
bytes = 23
#12 0x7f570e636d03 in exaCopyDirty (migrate=migrate@entry=0x7fffef000e40,
pValidDst=0x7f5713dc3e40, pValidSrc=0x7f5713dc3e50, transfer=0x7f570f28b7f0
nouveau_exa_download_from_screen, fallback_index=fallback_index@entry=1,
sync=0x7f570e635780 exaWaitSync) at ../../exa/exa_migration_classic.c:240
pPixmap = 0x7f5713dc3da0
pExaPixmap = 0x7f5713dc3e00
damage = optimized out
CopyReg = {extents = {x1 = 0, y1 = 0, x2 = 23, y2 = 16}, data = 0x0}
save_use_gpu_copy = 1
save_pitch = 64
pBox = 0x7fffef000de0
nbox = 1
access_prepared = 1
need_sync = 0
#13 0x7f570e636f32 in exaCopyDirtyToSys
(migrate=migrate@entry=0x7fffef000e40) at ../../exa/exa_migration_classic.c:285
pPixmap = optimized out
pExaScr = 0x7f5713877100
pExaPixmap = 0x0
#14 0x7f570e63951a in exaPrepareAccessReg_mixed (pPixmap=0x7f5713dc3da0,
index=optimized out, pReg=0x0) at ../../exa/exa_migration_mixed.c:254
as_dst = 1
pixmaps = {{as_dst = 0, as_src = 1, pPix = 0x7f5713dc3da0, pReg =
0x0}}
pExaPixmap = 0x7f5713dc3e00
has_gpu_copy = optimized out
success = optimized out
[Original Report]
The crash report started immediately after login.
ProblemType: CrashDistroRelease: Ubuntu 12.10
Package: xserver-xorg-core 2:1.12.99.902-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
Date: Sun Aug 5 14:46:44 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 4.1.18, 3.5.0-6-generic, x86_64: installed
virtualbox, 4.1.18, 3.5.0-8-generic, x86_64: installed
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation C61 [GeForce 6100 nForce 400] [10de:03d2] (rev a2)
(prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device [10de:cb84]
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120519)
Lsusb:
Bus 001 Device 002: ID 18ec:3399 Arkmicro Technologies Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcCmdline: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
-novtswitch -background none
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-8-generic
root=UUID=a80eff25-65c3-4db0-adad-31d8ea95823b ro quiet splash vt.handoff=7
Renderer: Software
Signal: 6SourcePackage: xorg-server
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
?? () from /usr/lib/xorg/modules/libexa.so
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/22/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: NF-MCP61
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/22/2006:svn:pn:pvr:rvn:rnNF-MCP61:rvr:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.37-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1
[Desktop-packages] [Bug 918444] Re: Firefox keeps crashing when browsing websites
Thanks, but this bug report is two years old... I have long since
forgotten about this, and I've upgraded Ubuntu (and changed hardware?) a
few times. I'm using Firefox 26.0 now, so I can't reproduce this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/918444
Title:
Firefox keeps crashing when browsing websites
Status in “firefox” package in Ubuntu:
Invalid
Bug description:
After I got the new Ubuntu update to version 9.0.1, I've had many
crashes, meaning that Firefox just vanishes and I get the report
error dialog. Today this has happened two or three times while
browsing the Norwegian finn.no site, a website to buy and sell stuff.
The first crash was when I opened the bookmark, I had another crash
when I tried to submit a search. I think the crashes always occur when
loading a page, and other websites may provoke this as well.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: firefox 9.0.1+build1-0ubuntu0.11.04.1
ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic i686
Architecture: i386
BuildID: 20111221202246
Date: Wed Jan 18 23:29:39 2012
DefaultProfileIncompatibleExtensions:
Google Toolbar for Firefox - ID={3112ca9c-de6d-4884-a869-9855de68056c},
Version=7.1.20110512L, minVersion=2.0, maxVersion=4.0.*, Location=app-profile,
Type=extension, Active=Yes
Elasticfox - ID={2204c510-88f3-11db-b606-0800200c9a66}, Version=1.7.000116,
minVersion=2.0, maxVersion=4.0, Location=app-profile, Type=extension, Active=Yes
NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232}, Version=2.2.6,
minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, Type=extension,
Active=Yes
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1Locales: extensions.sqlite corrupt or missing
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile0 (Default) - LastVersion=9.0.1/20111221202246 (Running)
Profile1 - LastVersion=3.6.12/20101027124101 (Out of date)
Profile2 - LastVersion=3.6.8/20100723084720 (Out of date)
SourcePackage: firefox
UpgradeStatus: Upgraded to natty on 2011-04-30 (263 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/918444/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268049] Re: Mouse wheel emulation non-functional with soft buttons
*** This bug is a duplicate of bug 1246683 *** https://bugs.launchpad.net/bugs/1246683 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1268049 Title: Mouse wheel emulation non-functional with soft buttons Status in “xorg” package in Ubuntu: Confirmed Bug description: When using a Lenovo T440S, and I believe any other notebook that uses a soft buttons on a clickpad to enable left/middle/right mouse clicking, wheel emulation does not work. Wheel emulation is functional when not using a hot button, but attempting to enable it when holding down middle button does not work. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 Uname: Linux 3.12.0-031200-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 11 11:01:55 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:220c] InstallationDate: Installed on 2013-12-17 (24 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20AQCTO1WW MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.12.0-031200-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET64WW (2.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET64WW(2.14):bd11/12/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Jan 9 08:48:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4669 vendor AUO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270783] [NEW] apport_python_hook.py fails in LXC container in with in get_logind_session No such file or directory: '/sys/fs/cgroup/systemd//user/1000.user/c2.session
Public bug reported:
In an up to date Trusty container run:
root@trusty-amd64:~# aa-status --enabled
Traceback (most recent call last):
[...]
Error in sys.excepthook:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport_python_hook.py, line 103, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File /usr/lib/python3/dist-packages/apport/report.py, line 546, in
add_proc_info
ret = self.get_logind_session(pid)
File /usr/lib/python3/dist-packages/apport/report.py, line 1601, in
get_logind_session
session_start_time = os.stat('/sys/fs/cgroup/systemd/' + my_cgroup).st_mtime
FileNotFoundError: [Errno 2] No such file or directory:
'/sys/fs/cgroup/systemd//user/1000.user/c2.session'
[...]
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.13.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportLog:
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CrashReports:
640:1000:136:773471:2014-01-20 08:58:46.153621912 +0100:2014-01-20
08:58:47.153621912 +0100:/var/crash/_usr_bin_indicator-weather.1000.crash
640:0:136:61574:2014-01-12 08:04:10.823513032 +0100:2014-01-12
08:04:10.747513035 +0100:/var/crash/_usr_lib_squid3_pinger.0.crash
CurrentDesktop: Unity
Date: Mon Jan 20 11:25:31 2014
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to trusty on 2012-01-31 (719 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2013-08-28T08:47:19.111940
** Affects: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1270783
Title:
apport_python_hook.py fails in LXC container in with in
get_logind_session No such file or directory:
'/sys/fs/cgroup/systemd//user/1000.user/c2.session
Status in “apport” package in Ubuntu:
New
Bug description:
In an up to date Trusty container run:
root@trusty-amd64:~# aa-status --enabled
Traceback (most recent call last):
[...]
Error in sys.excepthook:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport_python_hook.py, line 103, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File /usr/lib/python3/dist-packages/apport/report.py, line 546, in
add_proc_info
ret = self.get_logind_session(pid)
File /usr/lib/python3/dist-packages/apport/report.py, line 1601, in
get_logind_session
session_start_time = os.stat('/sys/fs/cgroup/systemd/' +
my_cgroup).st_mtime
FileNotFoundError: [Errno 2] No such file or directory:
'/sys/fs/cgroup/systemd//user/1000.user/c2.session'
[...]
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.13.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportLog:
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CrashReports:
640:1000:136:773471:2014-01-20 08:58:46.153621912 +0100:2014-01-20
08:58:47.153621912 +0100:/var/crash/_usr_bin_indicator-weather.1000.crash
640:0:136:61574:2014-01-12 08:04:10.823513032 +0100:2014-01-12
08:04:10.747513035 +0100:/var/crash/_usr_lib_squid3_pinger.0.crash
CurrentDesktop: Unity
Date: Mon Jan 20 11:25:31 2014
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to trusty on 2012-01-31 (719 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2013-08-28T08:47:19.111940
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1270783/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270788] [NEW] loggin out from guest session should notify that data will be cleared
Public bug reported: If logging out from the guest account resets it and clears all data, then the logout dialog should give a hint that all data will be reset and that the user should cancel if he/she wants to save files on a USB drive, or if he/she wants to ask the host/computer owner to copy the files to a persistent location. ** Affects: gdm-guest-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm-guest-session in Ubuntu. https://bugs.launchpad.net/bugs/1270788 Title: loggin out from guest session should notify that data will be cleared Status in “gdm-guest-session” package in Ubuntu: New Bug description: If logging out from the guest account resets it and clears all data, then the logout dialog should give a hint that all data will be reset and that the user should cancel if he/she wants to save files on a USB drive, or if he/she wants to ask the host/computer owner to copy the files to a persistent location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm-guest-session/+bug/1270788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270791] [NEW] Lightdm password wifi
Public bug reported: Lightdm does not store my wifi password, for classic wifi is ok it stores every password, but for eap/peap wifi configuration it doesn't store any password and it asks me every time wifi password before login. Bug recognized in ubuntu 13.04 and 13.10 and probably in ubuntu 14.04 (testing). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 11:52:45 2014 InstallationDate: Installed on 2013-12-28 (22 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- 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/1270791 Title: Lightdm password wifi Status in “lightdm” package in Ubuntu: New Bug description: Lightdm does not store my wifi password, for classic wifi is ok it stores every password, but for eap/peap wifi configuration it doesn't store any password and it asks me every time wifi password before login. Bug recognized in ubuntu 13.04 and 13.10 and probably in ubuntu 14.04 (testing). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 11:52:45 2014 InstallationDate: Installed on 2013-12-28 (22 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1270791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1152281] Re: evolution-calendar-factory crashed with SIGABRT in __libc_message()
This bug was fixed in the package evolution-data-server - 3.10.3-0ubuntu1 --- evolution-data-server (3.10.3-0ubuntu1) trusty; urgency=medium * New upstream version, drop git_uoa_calendar.patch included * debian/control: updated libgweather requirement * debian/patches/git_write_to_ldap.patch: - Unable to write to ldap addressbook * debian/patches/git_init_backend_sigabrt.patch - don't hit sigabrt in initialize_backend() (lp: #1152281) * debian/rules: disable hardening to workaround toolchain issues -- Sebastien Bacher seb...@ubuntu.com Fri, 17 Jan 2014 10:27:09 +0100 ** Changed in: evolution-data-server (Ubuntu) Status: Confirmed = Fix Released -- 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/1152281 Title: evolution-calendar-factory crashed with SIGABRT in __libc_message() Status in “evolution-data-server” package in Ubuntu: Fix Released Bug description: About 2 minutes after loging into ubuntu 13.04 this faultmessage appear. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: evolution-data-server 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9-0ubuntu2 Architecture: i386 Date: Thu Mar 7 19:33:40 2013 ExecutablePath: /usr/lib/evolution/evolution-calendar-factory InstallationDate: Installed on 2013-02-03 (31 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130202) MarkForUpload: True ProcCmdline: /usr/lib/evolution/evolution-calendar-factory ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANG=nl_NL.UTF-8 Signal: 6 SourcePackage: evolution-data-server StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: evolution-calendar-factory crashed with SIGABRT in raise() 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/evolution-data-server/+bug/1152281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1199074] Re: Saucy - cannot uninstall gnome-screensaver because it wants to uninstall gnome-session-flashback also.
This bug was fixed in the package gnome-panel - 1:3.8.0-1ubuntu3 --- gnome-panel (1:3.8.0-1ubuntu3) trusty; urgency=low * Rebuild for libgweather transition. * Remove gnome-screensaver from required components (LP: #1199074). -- Dmitry Shachnev mity...@ubuntu.com Thu, 16 Jan 2014 12:46:14 +0400 ** Changed in: gnome-panel (Ubuntu) Status: Triaged = Fix Released -- 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/1199074 Title: Saucy - cannot uninstall gnome-screensaver because it wants to uninstall gnome-session-flashback also. Status in “gnome-panel” package in Ubuntu: Fix Released Bug description: I wanted to uninstall gnome-screensaver and have xscreensaver work but, when I attempt to remove gnome-screensaver, it wants to take gnome-session-flashback. That is not what I want to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1199074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1215463] Re: Disable while typing should disable cursor movement
** Changed in: hundredpapercuts Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1215463 Title: Disable while typing should disable cursor movement Status in One Hundred Papercuts: Confirmed Status in System76: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: On a modern laptop with a large touchpad/clickpad, your palms tend to brush the touch surface as you type. The problem is that on Ubuntu, this creates an annoying amount of cursor wiggle. Competing platforms don't have this problem, so this needs to be improved on Ubuntu. Part of the problem is that `xserver-xorg-input-synaptics` driver doesn't do effective palm detection (it seems), and part of the problem is that `gnome-settings-daemon` launches `syndaemon` such that it *never* disables cursor movement. Currently syndaemon is launched like this: syndaemon -i 1.0 -t -K -R The -t option tells syndaemon to never block cursor movement. It will only block accidental vertical scrolling (which is darn near impossible to do on a modern system with two finger scrolling), and block accidental tap-to-click (which seems unlikely something you can do by mistake with your palms). So from a user perspective, Disable while typing currently does nothing. I'm proposing that syndaemon instead be launched like this: syndaemon -i 0.5 -K -R Without the -t option, syndaemon will block cursor movement, vertical scrolling, and tap-to-click. And the -i 0.5 means it will block it for 500ms (half a second). System76 has been shipping a patched `gnome-settings-daemon` (Raring) on all our products for the last two months, and we've received no support issues about it (if this caused noticeable usability issues, I'm confident we'd have heard about it). We've also done a lot of testing and tuning on the timeout threshold, and 500ms seems like about the sweet spot. It's long enough to be decently effective for most typists, but not so long that the user will catch the trackpad still disabled when they move from typing back to cursoring :P Note that this isn't a prefect solution, and you really can't do this especially well with a static timeout anyway (would be better to be dynamic based on typing speed). For slow typists, 500ms often isn't long enough. But for now, I feel it's better to find that sweet spot where it at least gives some improvement for most users, without causing any negative impact for any users. I have a Saucy package available for testing here: https://launchpad.net/~system76-dev/+archive/daily?field.series_filter=saucy And the proposed branch here: https://code.launchpad.net/~jderose/ubuntu/saucy/gnome-settings-daemon/tune-syndaemon2 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.6.4-0ubuntu16 ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 22 07:35:33 2013 MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1215463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 553527] Re: Installing Evolution should install evolution-indicator
This bug was fixed in the package evolution - 3.10.3-0ubuntu3 --- evolution (3.10.3-0ubuntu3) trusty; urgency=low [ Sebastien Bacher ] * debian/control.in: - Recommends evolution-indicator (lp: #553527) [ Martin Pitt ] * Fix Vcs-* to point to the right branch. * New upstream bug fix release. * 20_skip_broken_gconf_conversions.patch: Adjust for new release. * Bump libwebkitgtk-3.0-dev, libgweather-3-dev, and e-d-s build deps as per upstream configure.ac. -- Martin Pitt martin.p...@ubuntu.com Mon, 20 Jan 2014 10:50:14 +0100 ** Changed in: evolution (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/553527 Title: Installing Evolution should install evolution-indicator Status in Indicator Applet: Invalid Status in “evolution” package in Ubuntu: Fix Released Bug description: Ubuntu Lucid evolution 3.8.4-0ubuntu1, Ubuntu 13.10 1. Install Evolution. 2. Receive some messages. What should happen: The messages show up in the messaging menu. What happens: They don't. This is because evolution-indicator is not installed along with evolution. After installing Lucid, I decided to remove Evolution. After a few weeks I decided to reinstall Evolution, which I did. But if I get mail I don't see an indication to that effect on the indicator applet. I was assuming that installing Evolution will tie it with the applet, but that does not appear to be the case. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/553527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1182814] Re: [saucy] usb-modeswitch-data bad packaging forces removal of usb-modeswitch
** Changed in: hundredpapercuts Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1182814 Title: [saucy] usb-modeswitch-data bad packaging forces removal of usb- modeswitch Status in One Hundred Papercuts: Confirmed Status in “usb-modeswitch-data” package in Ubuntu: Confirmed Bug description: Ubuntu saucy has usb-modeswitch-data-20120815-1. Attempting to upgrade to the latest version usb-modeswitch-data-20121109-3 is impossible because of bad packaging which forces removal of usb-modeswitch!!! To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1182814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 435930] Re: Guest session does not warn about temporary nature of files
** Changed in: hundredpapercuts Importance: Undecided = Wishlist ** No longer affects: hundredpapercuts -- 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/435930 Title: Guest session does not warn about temporary nature of files Status in Ayatana Design: New Status in “lightdm” package in Ubuntu: In Progress Status in Baltix GNU/Linux: New Bug description: Hi all, this is not a bug per se, rather a request for a feature. One of the users I support has allowed someone to use his desktop using the Guest Session, not realising that files saved during this session do not persist after logout. The person in question proceeded to do a good few hours work on the machine, saving files to the Guest Session desktop. They were of course extremely dismayed when they logged in again, only to find that their work has disappeared. I think it would be a nice feature if, upon logging into the Guest Session, a splash screen appeared telling the user in no uncertain terms that any files they saved during the session would not persist after they logged out. I am a linux sysadmin and I was unaware of this property of the Guest Session and had to search online for an explanation for the behavior which, I'm sure you agree, is not ideal. Thanks in advance, Dan T. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/435930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1188509] Re: Embedded in menu doesn't work in IBus indicator
** Changed in: hundredpapercuts Importance: Undecided = High ** Changed in: hundredpapercuts Status: Confirmed = Triaged ** Changed in: hundredpapercuts Assignee: Papercuts Ninjas (papercuts-ninja) = (unassigned) -- 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/1188509 Title: Embedded in menu doesn't work in IBus indicator Status in One Hundred Papercuts: Triaged Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I've previously made video explain the difference between vanilla IBus 1.4.x and IBus indicator https://dl.dropboxusercontent.com/u/45139465/vanilla-ibus.ogv https://dl.dropboxusercontent.com/u/45139465/ibus-indicator.ogv In short, many IBus engines have their own context menu. In vanilla IBus1.4.x, it can either be embedded into tray icon or be shown in independent language panel. The default option is Embedded in menu, it embeds the context menu to tray icon. While other options When active and Always uses langauge panel. With IBus indicator, however, the context menu is totally invisible with the default option Embedded in menu. One has to manually enable When active or Always to access the per engine context menu. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1188509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201679] Re: ibus' Super+Space shortcut (usually) doesn't work
** Changed in: hundredpapercuts Assignee: Papercuts Ninjas (papercuts-ninja) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1201679 Title: ibus' Super+Space shortcut (usually) doesn't work Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: 1. Add the ubuntu-desktop PPA on Ubuntu 13.10 Saucy sudo add-apt-repository ppa:ubuntu-desktop/ppa sudo apt-get update sudo apt-get upgrade sudo apt-get install indicator-keyboard 2. Log out and log back in. 2. Open System SettingsRegion Language 3. Switch to the Text Entry tab. 4. Click the + button to add at least two more keyboard layouts. 5. Log out and log back in. 6. Try to use the (new) default Super+Space keyboard shortcut to switch between keyboard layouts. What happens --- Usually, Super+Space is ignored. It worked for me once on login but every other time I tested it didn't work. It works fine in GNOME Shell but not in Unity. gsettings reset org.gnome.settings-daemon.plugins.media-keys switch-input-source seems to be enough to nudge Unity into respecting the Super+Space keyboard shortcut. My guess is that Unity is too aggressive in binding the Super key to itself. Workaround - Shift+Super+Space, the keyboard shortcut to switch backward between keyboard layouts works. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jul 16 00:28:27 2013 InstallationDate: Installed on 2013-06-14 (31 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1201679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1180665] Re: gedit SIGSEGV in gedit_multi_notebook_get_active_tab()
** Changed in: hundredpapercuts Importance: Medium = High ** Changed in: hundredpapercuts Assignee: Papercuts Ninjas (papercuts-ninja) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1180665 Title: gedit SIGSEGV in gedit_multi_notebook_get_active_tab() Status in Light-Weight Text Editor for Gnome: New Status in One Hundred Papercuts: Triaged Status in “gedit” package in Ubuntu: Triaged Bug description: crashed with about 5 tabs open ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gedit 3.8.0-0ubuntu1~raring1 [origin: LP-PPA-gnome3-team-gnome3] ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.1-0ubuntu1 Architecture: amd64 Date: Thu May 16 12:26:21 2013 ExecutablePath: /usr/bin/gedit ExecutableTimestamp: 1367295250 InstallationDate: Installed on 2012-09-23 (235 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120922) MarkForUpload: True ProcCmdline: gedit ProcCwd: /home/darkness ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x460076 gedit_multi_notebook_get_active_tab+22: cmp%rax,(%rdx) PC (0x00460076) ok source %rax ok destination (%rdx) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_multi_notebook_get_active_tab () ?? () selection_received (widget=0x1e09dd0, selection_data=0x7fffd9d55a70, time=optimised out) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkclipboard.c:939 g_closure_invoke (closure=0x1fbe0e0, return_value=0x0, n_param_values=3, param_values=0x7fffd9d55720, invocation_hint=0x7fffd9d556c0) at /build/buildd/glib2.0-2.37.0/./gobject/gclosure.c:777 signal_emit_unlocked_R (node=node@entry=0x19c8db0, detail=detail@entry=0, instance=instance@entry=0x1e09dd0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd9d55720) at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c:3584 Title: gedit crashed with SIGSEGV in gedit_multi_notebook_get_active_tab() 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/gedit/+bug/1180665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1263559] Re: Every opened tab give crash report. No longer useable.
Martin Schaaf, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/1263559 Title: Every opened tab give crash report. No longer useable. Status in “chromium-browser” package in Ubuntu: Invalid Bug description: I see this in dmesg output: [ 1915.915286] chromium-browse[5971]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1954.671817] chromium-browse[5985]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1959.798685] chromium-browse[5990]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1963.357938] chromium-browse[5994]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1963.733380] chromium-browse[5998]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1963.862840] chromium-browse[6002]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1964.024203] chromium-browse[6006]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1964.314183] chromium-browse[6014]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1964.365788] chromium-browse[6010]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1964.561884] chromium-browse[6023]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1964.682437] chromium-browse[6027]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1978.187765] chromium-browse[6083]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1978.434328] chromium-browse[6079]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1978.459672] chromium-browse[6087]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1979.511827] chromium-browse[6094]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1986.720367] chromium-browse[6104]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1991.416580] chromium-browse[6110]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in libc-2.17.so[7f21dc48e000+1bf000] [ 1991.701547] chromium-browse[6114]: segfault at 7fff2005fff8 ip 7f21dc50f026 sp 7fff2006 error 6 in
[Desktop-packages] [Bug 1270794] [NEW] Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x00007f1352d5f370 ***
Public bug reported: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** The Chromium browser has been crashed when I try to write a downloaded file on a NFTS file system device. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AssertionMessage: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Date: Mon Jan 20 10:47:12 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser ExecutableTimestamp: 1386651735 InstallationDate: Installed on 2013-07-13 (190 days ago) InstallationMedia: Ubuntu 13.04 - Release amd64 (20130428) MarkForUpload: True ProcCmdline: chromium-browser ProcCwd: /home/neptune2 Signal: 6 SourcePackage: chromium-browser StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f133bc0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x7f1352d5f370, str=0x7f133bc40405 free(): invalid pointer, action=3) at malloc.c:4923 _int_free (av=optimized out, p=0x7f1352d5f360, have_lock=0) at malloc.c:3779 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'elementary-xfce-dark\n'/desktop/gnome/interface/gtk_theme = b'Greybird\n' ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace raring third-party-packages ** Information type changed from Private to Public -- 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/1270794 Title: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Status in “chromium-browser” package in Ubuntu: New Bug description: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** The Chromium browser has been crashed when I try to write a downloaded file on a NFTS file system device. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AssertionMessage: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Date: Mon Jan 20 10:47:12 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser ExecutableTimestamp: 1386651735 InstallationDate: Installed on 2013-07-13 (190 days ago) InstallationMedia: Ubuntu 13.04 - Release amd64 (20130428) MarkForUpload: True ProcCmdline: chromium-browser ProcCwd: /home/neptune2 Signal: 6 SourcePackage: chromium-browser StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f133bc0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x7f1352d5f370, str=0x7f133bc40405 free(): invalid pointer, action=3) at malloc.c:4923 _int_free (av=optimized out, p=0x7f1352d5f360, have_lock=0) at malloc.c:3779 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** UpgradeStatus: No upgrade log
[Desktop-packages] [Bug 1205647] Re: gvfsd-smb crashes when been unmounted from Nautilus
** Changed in: hundredpapercuts Importance: Low = Medium ** Changed in: hundredpapercuts Assignee: Papercuts Ninjas (papercuts-ninja) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1205647 Title: gvfsd-smb crashes when been unmounted from Nautilus Status in GVFS: Confirmed Status in One Hundred Papercuts: Triaged Status in “gvfs” package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE 1. Open a Nautilus window. 2. Open a new tab. 3. In the new tab, navigate to a Samba share. 4. A new entry for the share appears under Network in the left side panel. 5. Close the new tab. 6. In the left side panel, under Network, click the unmount icon next to Samba share entry. ** EXPECTED BEHAVIOUR ** - Samba share to be unmounted. ** REAL BEHAVIOUR ** - gvfsd-smb crashes. - Get two alert boxes: 1. Oops! Something went wrong. Unhandled error message: The connection is closed 2. Unable to unmount share name The connection is closed ** TECHNICAL INFO ** ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gvfs-backends 1.17.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Sat Jul 27 15:58:03 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-smb InstallationDate: Installed on 2013-07-20 (6 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=fr_FR LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x7fad3ebbfff1:cmpb $0x0,(%rax) PC (0x7fad3ebbfff1) ok source $0x0 ok destination (%rax) (0x0170) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 ?? () g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gvfsd-smb crashed with SIGSEGV in g_vfs_job_run() UpgradeStatus: Upgraded to saucy on 2013-07-20 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1205647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 607141] Re: Cups: Translation template should be in the binary package, not in the langpack
** Changed in: hundredpapercuts Assignee: Papercuts Ninjas (papercuts-ninja) = (unassigned) ** Changed in: hundredpapercuts Status: New = Triaged ** Changed in: hundredpapercuts Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/607141 Title: Cups: Translation template should be in the binary package, not in the langpack Status in CUPS - Common Unix Printing System: New Status in One Hundred Papercuts: Triaged Status in Ubuntu Translations: Triaged Status in “cups” package in Ubuntu: Triaged Bug description: Currently, we export the cups template along the other .mo files in the language packs. This is however, not what the software expects, thus not useful at all. Cups expects the files to be in /usr/share/cups/locale/ll, in the file name format of cups_ll.po and in PO format[1]. The cups-common package ships the existing translations this way: http://packages.ubuntu.com/lucid/all/cups-common/filelist So, what we should do is: -stop distributing the .mo files -add cups to the https://wiki.ubuntu.com/NonLanguagePackTranslationDeadline page, and export translations before Maverick is out. [1]: seems that while cups uses the po format for translation, it does not use gettext for using the translations in the code, but reads directly the po files. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/607141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1099592] Re: chrome quits after 2 seconds since system update
kif pow, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/1099592 Title: chrome quits after 2 seconds since system update Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Ubuntu 11.10 update manager trashed my chrome browser this morning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1099592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219964] Re: Kernel Panic while editing Gmail
Cefn, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux REPLACE-WITH-BUG-NUMBER If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.13-rc8 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Package changed: chromium-browser (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Tags added: needs-kernel-logs needs-upstream-testing -- 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/1219964 Title: Kernel Panic while editing Gmail Status in “linux” package in Ubuntu: Incomplete Bug description: Hi there, I seem to hit kernel panics while running chromium-browser recently. At the point of the last kernel panic I was typing in Gmail, with only audio running otherwise. I have Flash disabled on all tabs by default, so I don't think there's anything outside the Open source code running (unless previous flash instances hang around as zombies somehow). Is there a way I can retain the chromium session to pass on debug info? Guess it'll be tricky without handing over a load of my cookie info. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 28.0.1500.71-0ubuntu3 Uname: Linux 3.11.0-031100rc6-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 Date: Mon Sep 2 20:30:43 2013 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-08-15 (18 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha i386 (20130626) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1065961] Re: chromium-browser: general protection (fault)
Dennis Schridde, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/1065961 Title: chromium-browser: general protection (fault) Status in Chromium Browser: Unknown Status in “chromium-browser” package in Ubuntu: Invalid Bug description: chromium-browser crashes very often on my system, leaving the following in dmesg (excerpt): [69260.837159] chromium-browse[21110] general protection ip:b55fdfe9 sp:bf9caab0 error:0 in chromium-browser[b3206000+456a000] [69794.178272] chromium-browse[22905] general protection ip:b55defe9 sp:bf86fbc0 error:0 in chromium-browser[b31e7000+456a000] [69885.166766] chromium-browse[23139] general protection ip:b5642fe9 sp:bff37c50 error:0 in chromium-browser[b324b000+456a000] [71048.467893] chromium-browse[23287] general protection ip:b5619fe9 sp:bfe5f4c0 error:0 in chromium-browser[b3222000+456a000] [71110.682438] chromium-browse[24111]: segfault at 6 ip 4b98bace sp bfce6380 error 4 in libflashplayer.so[4b1f5000+1014000] I usually get an application-crashed information in the systray, but due to apport bug #1058376, no crash report ever gets send to Launchpad. This does not seem to depend on the website being looked at. It appears randomly and is not reproducible when watching the same website again. It seems to happen only when leaving one page / loading another, but never when the page is already loaded. Sometimes Chromium does not crash, but freezes instead and has to be killed. It happens only since a few weeks (maybe 1-2 months at max), so it could be caused by an update to some library. Chromium was also updated during that timeframe: chromium-browser:i386 (18.0.1025.168~r134367-0ubuntu0.12.04.1, 20.0.1132.47~r144678-0ubuntu0.12.04.1), from /var/log/apt/history.log. I downgraded to a version archived on Launchpad [1], which does not show the bug. Version: 20.0.1132.47~r144678-0ubuntu0.12.04.1 [1] https://launchpad.net/ubuntu/+source/chromium-browser/18.0.1025.168~r134367-0ubuntu0.12.04.1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Fri Oct 12 14:27:48 2012 Desktop-Session: DESKTOP_SESSION = default XDG_CONFIG_DIRS = /etc/xdg/xdg-default:/etc/xdg XDG_DATA_DIRS = /usr/share/default:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: LANGUAGE= TERM=screen LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to:
[Desktop-packages] [Bug 1270794] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1270794/+attachment/3952746/+files/Stacktrace.txt -- 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/1270794 Title: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Status in “chromium-browser” package in Ubuntu: New Bug description: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** The Chromium browser has been crashed when I try to write a downloaded file on a NFTS file system device. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AssertionMessage: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Date: Mon Jan 20 10:47:12 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser ExecutableTimestamp: 1386651735 InstallationDate: Installed on 2013-07-13 (190 days ago) InstallationMedia: Ubuntu 13.04 - Release amd64 (20130428) MarkForUpload: True ProcCmdline: chromium-browser ProcCwd: /home/neptune2 Signal: 6 SourcePackage: chromium-browser StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f133bc0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x7f1352d5f370, str=0x7f133bc40405 free(): invalid pointer, action=3) at malloc.c:4923 _int_free (av=optimized out, p=0x7f1352d5f360, have_lock=0) at malloc.c:3779 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'elementary-xfce-dark\n'/desktop/gnome/interface/gtk_theme = b'Greybird\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1270794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1064062] Re: Chromium keeps crashing
teddy tran, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/1064062 Title: Chromium keeps crashing Status in “chromium-browser” package in Ubuntu: Invalid Bug description: It does not matter if I have one tab open, or four tabs open. I update quite frequently, and this problem starting occuring about 1 month ago. I have used xubuntu since 12.04 was released. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Mon Oct 8 13:54:29 2012 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1064062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965314] [NEW] core dumped - segmentation fault
You have been subscribed to a public bug: In Precise Chromium always crash at first start. core dumped - segmentation fault I haven't found any other log about it, ask if needed! :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 17.0.963.83~r127885-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:55:44 2012 Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug precise -- core dumped - segmentation fault https://bugs.launchpad.net/bugs/965314 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1030685] Re: crashes in gssapi stack
** Package changed: chromium-browser (Ubuntu) = linuxmint -- 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/1030685 Title: crashes in gssapi stack Status in The Linux Mint Distribution: New Bug description: While trying to upload an attachment to a Trac bug tracking system, chromium crashes with 100% reproducibility. There is the stacktrace from the crash. I have a /var/crash apport file from the crash but I will not be furnishing it due to the huge security leak potential of posting core dumps. I am happy to extract whatever information you need from it however, such as this stack trace of the segfaulting thread: #0 krb5_gss_inquire_context (minor_status=0xabb31888, context_handle=0x0, initiator_name=0xabb3121c, acceptor_name=0xabb31218, lifetime_rec=0xabb31894, mech_type=0x0, ret_flags=0xabb3189c, locally_initiated=0xabb318a0, opened=0xabb318a4) at ../../../../src/lib/gssapi/krb5/inq_context.c:108 #1 0xb216433f in gss_inquire_context (minor_status=0xabb31888, context_handle=0xbdfd0ed0, src_name=0xabb3188c, targ_name=0xabb31890, lifetime_rec=0xabb31894, mech_type=0xabb31898, ctx_flags=0xabb3189c, locally_initiated=0xabb318a0, opened=0xabb318a4) at ../../../../src/lib/gssapi/mechglue/g_inq_context.c:113 #2 0xb45c8691 in net::GSSAPISharedLibrary::inquire_context(unsigned int*, gss_ctx_id_struct*, gss_name_struct**, gss_name_struct**, unsigned int*, gss_OID_desc_struct**, unsigned int*, int*, int*) () #3 0xb45cac45 in net::HttpAuthGSSAPI::GetNextSecurityToken(std::basic_stringwchar_t, std::char_traitswchar_t, std::allocatorwchar_t const, gss_buffer_desc_struct*, gss_buffer_desc_struct*) () #4 0xb45cb75e in net::HttpAuthGSSAPI::GenerateAuthToken(net::AuthCredentials const*, std::basic_stringwchar_t, std::char_traitswchar_t, std::allocatorwchar_t const, std::string*) () #5 0xb44e7532 in net::HttpAuthHandlerNegotiate::DoGenerateAuthToken() () #6 0xb44e75b8 in net::HttpAuthHandlerNegotiate::DoLoop(int) () #7 0xb44e7667 in net::HttpAuthHandlerNegotiate::GenerateAuthTokenImpl(net::AuthCredentials const*, net::HttpRequestInfo const*, base::Callbackvoid (int) const, std::string*) () #8 0xb45cc1c7 in net::HttpAuthHandler::GenerateAuthToken(net::AuthCredentials const*, net::HttpRequestInfo const*, base::Callbackvoid (int) const, std::string*) () #9 0xb45c7f3c in net::HttpAuthController::MaybeGenerateAuthToken(net::HttpRequestInfo const*, base::Callbackvoid (int) const, net::BoundNetLog const) () #10 0xb44f9bff in net::HttpNetworkTransaction::DoGenerateProxyAuthToken() () #11 0xb44f9f08 in net::HttpNetworkTransaction::DoLoop(int) () #12 0xb44fa138 in net::HttpNetworkTransaction::OnIOComplete(int) () #13 0xb4515aca in net::HttpStreamFactoryImpl::Request::OnStreamReady(net::HttpStreamFactoryImpl::Job*, net::SSLConfig const, net::ProxyInfo const, net::HttpStream*) () #14 0xb450d155 in net::HttpStreamFactoryImpl::Job::OnStreamReadyCallback() () #15 0xb450d8a4 in base::internal::Invoker1, base::internal::BindStatebase::internal::RunnableAdaptervoid (net::HttpStreamFactoryImpl::Job::*)(), void (net::HttpStreamFactoryImpl::Job*), void (base::WeakPtrnet::HttpStreamFactoryImpl::Job), void (net::HttpStreamFactoryImpl::Job*)::Run(base::internal::BindStateBase*) () #16 0xb41c4d0f in MessageLoop::RunTask(base::PendingTask const) () #17 0xb41c814c in MessageLoop::DeferOrRunPendingTask(base::PendingTask const) () #18 0xb41c8726 in MessageLoop::DoWork() () #19 0xb41a1898 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () #20 0xb41c4332 in MessageLoop::RunInternal() () #21 0xb41c4391 in MessageLoop::Run() () #22 0xb41e747b in base::Thread::Run(MessageLoop*) () #23 0xb41e73e2 in base::Thread::ThreadMain() () #24 0xb41e4cbc in base::(anonymous namespace)::ThreadFunc(void*) () #25 0xb2a50d4c in start_thread (arg=0xabb32b40) at pthread_create.c:308 #26 0xb258bace in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 ProblemType: Bug DistroRelease: LinuxMint 12 Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 NonfreeKernelModules: ksplice_dewe07wg_vmlinux_new ksplice_dewe07wg ksplice_t0vennht_vmlinux_new ksplice_t0vennht ksplice_xmujt7c9_vmlinux_new ksplice_xmujt7c9 ksplice_l34fkoxc_ttm_new ksplice_l34fkoxc ksplice_3e1g28bz_vmlinux_new ksplice_3e1g28bz ksplice_4qv4fmpp_vmlinux_new ksplice_4qv4fmpp ksplice_r0kvmav6_vmlinux_new ksplice_r0kvmav6 ksplice_20ua8hym ksplice_ifvi3ya6 ksplice_dde1axkc ksplice_s4l4rfyg ksplice_unoti1kb_snd_usb_audio_new ksplice_unoti1kb ksplice_7he9oi11 ksplice_ik8iovr1 ksplice_obg057es_vmlinux_new ksplice_obg057es ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Sun Jul 29 22:29:09 2012
[Desktop-packages] [Bug 1009534] Re: Flash plugin crashes with SIGILL on ThinkPad X30
*** This bug is a duplicate of bug 1009430 *** https://bugs.launchpad.net/bugs/1009430 ** This bug has been marked a duplicate of bug 1009430 Flash plugin crashes with SIGILL on ThinkPad X30 -- 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/1009534 Title: Flash plugin crashes with SIGILL on ThinkPad X30 Status in “chromium-browser” package in Ubuntu: New Bug description: See bug 1009430 for details. This bug exists to capture the Chromium version of the crash. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Wed Jun 6 15:21:21 2012 Desktop-Session: DESKTOP_SESSION = ubuntu-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423.2) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1009534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057925] Re: Chromium quits suddenly when browsing the web normally.
Duy Anh, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/1057925 Title: Chromium quits suddenly when browsing the web normally. Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Chromium quits suddenly when browsing the web normally. This bug, which doesn't appear in older version, happens after i update Chrome 18 - 20 with high frequency. I tried Google Chrome 20 - 21 and so do they. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Fri Sep 28 13:46:32 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.1) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1057925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054557] Re: Chromium 20.0.1132.47 and 21.0.1180.89 keep crashing silently
Benjamin Hilton, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/1054557 Title: Chromium 20.0.1132.47 and 21.0.1180.89 keep crashing silently Status in “chromium-browser” package in Ubuntu: Invalid Bug description: At seemingly random times, though often after launch, chromium exits with no error message. When it is started up again, there is a bar at the top of the screen saying that chromium did not shut down properly, with a button to restore tabs. Clicking the button often results in chromium crashing again. I am using Ubuntu 12.04.1 LTS (64-bit). I tried running chromium-browser from the command line, and when it crashes, the following message shows: Segmentation fault (core dumped). about:version outputs: Chromium 20.0.1132.47 (Developer Build 144678) Ubuntu 12.04 OSLinux WebKit536.11 (trunk@116185) JavaScriptV8 3.10.8.19 Flash 11.2 r202 User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.11 (KHTML, like Gecko) Ubuntu/12.04 Chromium/20.0.1132.47 Chrome/20.0.1132.47 Safari/536.11 Command Line /usr/lib/chromium-browser/chromium-browser --flag-switches-begin --enable-sync-tabs --flag-switches-end Executable Path /usr/lib/chromium-browser/chromium-browser Profile Path /home/benjamin/.config/chromium/Default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1054557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057327] Re: Dumps to login when rendering in chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1
Robert Grønning, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg REPLACE-WITH-BUG-NUMBER Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Package changed: chromium-browser (Ubuntu) = xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- 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/1057327 Title: Dumps to login when rendering in chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1 Status in “xorg” package in Ubuntu: Incomplete Bug description: When I open chromium-browser (20.0.1132.47~r144678-0ubuntu0.12.04.1) and try to make it render anything, I immediately loose the desktop and end up at login. I have tried to install classic gnome wihtout Unity, but no difference. What works is to install the previous version of chromium browser (apt-get install chromium- browser=18.0.1025.168~r134367-0ubuntu0.12.04.1) $ uname -a Linux torgerde 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 12.04.1 LTS Release: 12.04 Codename: precise Let me know if there are any specific logs you'd like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1057327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054635] Re: Chromium crashes when I enter facebook
Jarno Suni, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/1054635 Title: Chromium crashes when I enter facebook Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Steps to reproduce: enter url https://www.facebook.com and go. Login to facebook. Result: browser crashes Expected result: guess what? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sat Sep 22 18:36:36 2012 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2012-09-22 (0 days ago) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1054635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060174] Re: Attempting to open Bookmarks imported from Firefox crashes Chromium
Glenn Brumfield, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1060174/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/1060174 Title: Attempting to open Bookmarks imported from Firefox crashes Chromium Status in “chromium-browser” package in Ubuntu: Invalid Bug description: After installing Chromium, I imported bookmarks from Firefox. Attempting to open the Ubuntu Forums Bookmark that I imported from Firefox crashes Chromium. When Chromium is reopened, it reports that it has shut down incorrectly. Bookmarks operate correctly in Firefox. Bookmarks originated in Chromium work correctly. Ubuntu 12.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 CheckboxSubmission: b5f5c7bc16a7f581f291fede80c2dbf8 CheckboxSystem: 3935143777c965daaa64b51f0134f712 Date: Tue Oct 2 07:45:06 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1060174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1055533] Re: Chromium repeatedly crashes
Gabor Toth, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** This bug is no longer a duplicate of bug 1054557 Chromium 20.0.1132.47 and 21.0.1180.89 keep crashing silently ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/1055533 Title: Chromium repeatedly crashes Status in “chromium-browser” package in Ubuntu: Invalid Bug description: About a week ago got an update for the Chromium package. I did that update (and all updates before and since for the system) and since then Chromium became quite unstable. It has crashed numerous times. Seems randomly. Sometimes with 1 sometimes with 2 or more page open. Sometimes it has crashed then I reopened and crashed again. Then it was stable now for some days but today again crashed. I got a crash window opening but it somehow fails to generate an actual crash report so I am doing here manually. Right now Chromium works and I am typing this in Chromium. I am using UBUNTU 12.04, all updates are done, it is a Dell Inspiron 17R laptop with 4GB RAM, single boot environment. Tell me if more data is needed. Can not reproduce it when I want but happens quite often. Gabor ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 20.0.1132.47~r144678-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 CheckboxSubmission: f3b32d482d910d3ef76053b67a93d4c2 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Mon Sep 24 16:33:49 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) ProcEnviron: SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1055533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1265127] Re: 'CTRL +SHIFT+ALT+R' for screen recording are not working
** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided = Wishlist ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1265127 Title: 'CTRL +SHIFT+ALT+R' for screen recording are not working Status in Ubuntu GNOME: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Bug description: 'Print Scr' key for screenshots (are Fixed) 'CTRL+SHIFT+ALT+R' for screen recording not working. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: gnome-shell 3.10.2.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3] ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 31 05:31:35 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.shell.calendar' b'show-weekdate' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b'gtk-im-context-simple' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2013-12-30 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131230)SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1265127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965314] Re: core dumped - segmentation fault
** No longer affects: chromium-browser (Ubuntu) ** Changed in: chromium-browser Importance: Unknown = Undecided ** Changed in: chromium-browser Status: Unknown = New ** Changed in: chromium-browser Remote watch: code.google.com/p/chromium/issues #121660 = None -- 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/965314 Title: core dumped - segmentation fault Status in “chromium-browser” package in Ubuntu: Invalid Bug description: In Precise Chromium always crash at first start. core dumped - segmentation fault I haven't found any other log about it, ask if needed! :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 17.0.963.83~r127885-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:55:44 2012 Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965314] Re: core dumped - segmentation fault
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New = Confirmed -- 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/965314 Title: core dumped - segmentation fault Status in “chromium-browser” package in Ubuntu: Invalid Bug description: In Precise Chromium always crash at first start. core dumped - segmentation fault I haven't found any other log about it, ask if needed! :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 17.0.963.83~r127885-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:55:44 2012 Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965314] Re: core dumped - segmentation fault
Lucazade, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Project changed: chromium-browser = chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid ** Attachment removed: chromium.core.20120429.gz https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120504/+files/chromium.core.20120429.gz ** Attachment removed: chromium.core.20120430.gz https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120508/+files/chromium.core.20120430.gz ** Attachment removed: chromium.bug.20120430 https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+attachment/3120526/+files/chromium.bug.20120430 -- 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/965314 Title: core dumped - segmentation fault Status in “chromium-browser” package in Ubuntu: Invalid Bug description: In Precise Chromium always crash at first start. core dumped - segmentation fault I haven't found any other log about it, ask if needed! :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 17.0.963.83~r127885-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Mon Mar 26 13:55:44 2012 Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/965314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220681] Re: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Inval
This is reproduced in the automatic upgrade testing: http://d-jenkins.ubuntu-ci:8080/view/Upgrade/job/upgrade-ubuntu- quantal-trusty-desktop-i386/3/console Sorry, not viewable to non-Canonical folks yet, and not yet mirrored to jenkins.qa.ubuntu.com ** Summary changed: - package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami + package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link ** Changed in: espeak (Ubuntu) Status: New = Confirmed ** Description changed: automated report during do-release-upgrade -s -d + + relevant log + Preparing to replace espeak-data:i386 1.46.02-2ubuntu1 (using .../espeak-data_1.47.11-1_i386.deb) ... + Unpacking replacement espeak-data:i386 ... + dpkg: error processing /var/cache/apt/archives/espeak-data_1.47.11-1_i386.deb (--unpack): + unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link + --- ProblemType: Package DistroRelease: Ubuntu 13.10 Package: espeak-data 1.46.02-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CheckboxSubmission: b5c71cdd2e648a5dc8e6dfd1c7c6007f CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Wed Sep 4 13:26:42 2013 Dependencies: - + DuplicateSignature: package:espeak-data:1.46.02-2ubuntu1:ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami ErrorMessage: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami InstallationDate: Installed on 2011-02-25 (921 days ago) InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True SourcePackage: espeak Title: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami UpgradeStatus: Upgraded to saucy on 2013-09-04 (0 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to espeak in Ubuntu. https://bugs.launchpad.net/bugs/1220681 Title: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link Status in “espeak” package in Ubuntu: Confirmed Bug description: automated report during do-release-upgrade -s -d relevant log Preparing to replace espeak-data:i386 1.46.02-2ubuntu1 (using .../espeak-data_1.47.11-1_i386.deb) ... Unpacking replacement espeak-data:i386 ... dpkg: error processing /var/cache/apt/archives/espeak-data_1.47.11-1_i386.deb (--unpack): unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link --- ProblemType: Package DistroRelease: Ubuntu 13.10 Package: espeak-data 1.46.02-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CheckboxSubmission: b5c71cdd2e648a5dc8e6dfd1c7c6007f CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Wed Sep 4 13:26:42 2013 Dependencies: DuplicateSignature: package:espeak-data:1.46.02-2ubuntu1:ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami ErrorMessage: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami InstallationDate: Installed on 2011-02-25 (921 days ago) InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True SourcePackage: espeak Title: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami UpgradeStatus: Upgraded to saucy on 2013-09-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/espeak/+bug/1220681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1035932] Re: Chromium crashes very often on Ubuntu 12.04 with SIGSEGV in ??()
Patryk, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/1035932 Title: Chromium crashes very often on Ubuntu 12.04 with SIGSEGV in ??() Status in “chromium-browser” package in Ubuntu: Invalid Bug description: While working with Chromium on Ubuntu 12.04 the browser crashes often under various circumstances and at different time intervals. This is an example of gdb dump from command line : (exe:4208): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed (exe:4208): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed (exe:4208): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed [Thread 0x7fffe196e700 (LWP 1182) exited] [New Thread 0x7fffd2146700 (LWP 1212)] [Thread 0x7fffd2146700 (LWP 1212) exited] [New Thread 0x7fffe196e700 (LWP 1213)] Program received signal SIGSEGV, Segmentation fault. 0x in ?? () I use Nvidia drivers and in the debug log I often get something like ( I do not know if this is related) Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory ( and I also would like to mentioned that I have been affected by this problem http://askubuntu.com/questions/117127/flash-video-appears-blue so I have installed libvdpau1 and now I only have it installed instead of the original one http://askubuntu.com/questions/117127/flash-video-appears-blue USER@UBUNTU:~$ dpkg -l | grep libvdpau ii libvdpau1 0.4.1-3ubuntu1+fixbluefaces~precise ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 20.0.1132.47~r144678-0precise1+webapps5 [origin: LP-PPA-webapps-preview] ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CrashDB: ubuntu Date: Sun Aug 12 20:48:32 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1035932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270800] [NEW] Losing text fields focus when changing keyboard's layout
Public bug reported: Hello. There is a moment with changing keyboard's layout in 13.10 (and it was in 12.10, but the focus was returning immediately so I could type in new language in the moment). I change it using Alt+Shift. While I'm pressing on theese buttons, the focus is left from any textfield (single lines, many lines). It causes some problems. The first is that focus doesn't return immediately, so sometimes if I type very fast, the first letters I typed after the changing will not be shown. The second is that some programs select all text in the box when the focus returned (for example Flash), so I need to put the caret in the right position. The third is sending useless in this situation onfocus events. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,move,grid,snap,mousepoll,animation,imgpng,vpswitch,resize,place,compiztoolbox,unitymtgrabhandles,gnomecompat,firepaint,wall,expo,fade,workarounds,session,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 43.768071] input: Logitech Unifying Device. Wireless PID:101a as /devices/pci:00/:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0005/input/input14 [ 43.768389] logitech-djdevice 0003:046D:C52B.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101a] on usb-:00:14.0-3:1 Date: Mon Jan 20 17:22:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-15-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056a] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 7670M [1028:056a] InstallationDate: Installed on 2014-01-19 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. Inspiron 5520 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=4804716b-af02-4e50-a9ad-429ab057c291 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0XWH1P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/18/2012:svnDellInc.:pnInspiron5520:pvrA06:rvnDellInc.:rn0XWH1P:rvrA00:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5520 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Jan 20 16:36:02 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8428 vendor AUO xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1270800 Title: Losing text fields focus when changing keyboard's layout Status in “unity” package in Ubuntu: New Bug description: Hello. There is a moment with changing keyboard's layout in 13.10 (and it was in 12.10, but the focus was returning immediately so I could type in new language in the moment). I change it using Alt+Shift. While I'm pressing on theese buttons, the focus is left from any textfield (single lines, many lines). It causes some problems. The first is that focus doesn't
[Desktop-packages] [Bug 908275] Re: Crashes occasionally
Jarno Suni, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/908275 Title: Crashes occasionally Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Chromium 15.0.874.106 Ubuntu 11.10 Set the browser to reopen tabs from last session; use only one tab that has gmail.com (expanded). When started from terminal, it displays [5753:5773:3349945067:ERROR:x509_certificate_nss.cc(810)] CERT_PKIXVerifyCert for mail.google.com failed err=-8181 chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Aborted (the message may vary from time to time.) Restarting the browser or reloading the page might also crash the browser. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/908275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035768] Re: [ICE1712 - M Audio Audiophile 24/96, playback] no sound after suspend/resume in 12.04
Ahren Fitzroy's solution worked perfectly for me a year and a half on! Thank you! Much better than the useless forum threads that just tail off and the bug reports that have gone unanswered by Canonical. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1035768 Title: [ICE1712 - M Audio Audiophile 24/96, playback] no sound after suspend/resume in 12.04 Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I have perfectly fine sound playback from my Audiophile 2496 card on initial boot, but every time without fail when I suspend I have no audio upon resuming. When sound is gone after resume, activity can still be seen on the VU meters of envy24control when a sound is played. I found and tried a few recommendations online for dealing with similar problems, to no avail. Specifically: Running killall pulseaudio does not solve the problem. Running sudo alsa force-reload does not solve the problem. Logging out and back in does not solve the problem. Disabling my onboard Intel HD audio in the BIOS does not solve the problem. Adding options snd-ice1712 model=audiophile to the end of my /etc/modprobe.d/alsa-base.conf file does not solve the problem. The only thing that DOES solve the problem is a full reboot, which works every time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ahren 1931 F pulseaudio /dev/snd/controlC3: ahren 1931 F pulseaudio /dev/snd/controlC0: ahren 1931 F pulseaudio /dev/snd/controlC2: ahren 1931 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfdff4000 irq 44' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1028020d,0011' Controls : 41 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'SP2208WFP'/'Mic-OmniVision Technologies, Inc.538-2640-07.08.09.6 Monitor Webcam (SP2208WFP)' Mixer name : 'USB Mixer' Components : 'USB05a9:2643' Controls : 4 Simple ctrls : 3 Card2.Amixer.info: Card hw:2 'M2496'/'M Audio Audiophile 24/96 at 0xbf00, irq 16' Mixer name : 'ICE1712 - multitrack' Components : '' Controls : 48 Simple ctrls : 26 Card3.Amixer.info: Card hw:3 'HDMI'/'HDA ATI HDMI at 0xfddfc000 irq 45' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 6 Simple ctrls : 1 Card3.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sat Aug 11 20:12:25 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: RV630 audio device [Radeon HD 2600 Series] - HDA ATI HDMI Symptom_Type: Sound works for a while, then breaks Title: [ICE1712 - M Audio Audiophile 24/96, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-08-05T16:06:25.692043 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1035768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1180157] Re: Xorg freeze
The directory link you sent was for Trusty, so I downloaded and tried that. Hence, I've tried and found the bug present on Ubuntu 12.10, 13.04, Trusty, and also Fedora 18, and Fedora 19 - i.e. everything every put on this machine. On 2014-01-17 21:10, Christopher M. Penalver wrote: Thomas Lynch, thank you for providing the requested information. Did this problem not occur in Precise? ** Tags added: latest-bios-1.10 ** Tags added: quantal raring -- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1180157 Title: Xorg freeze Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: This bug is in 12.10 13.04 and 13.10 (I've been waiting to see if would go away ;-) When the system comes back from suspend the screen is black. Changing virtual terminals does nothing. If I have a program that makes sound, such as Alarm Clock the sound plays. I.e. the system appears to be alive but lacking a screen driver. Cntrl-Alt-Del has no noticable result. The only way out of this state I can figure out is to re-power the machine. A system update recently changed the close lid back to suspend, so closing the lid kills the video. I suppose it is clear from the uploaded information, but just in case, this is an Acer 7250. Thanks! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 14 18:04:58 2013 DistUpgraded: 2013-05-13 06:34:25,310 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0614] InstallationDate: Installed on 2012-11-12 (183 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Acer Aspire 7250 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-1-generic root=UUID=30739fe6-5586-4efa-bc0c-706e1283ff31 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to saucy on 2013-05-13 (1 days ago) dmi.bios.date: 11/02/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: HMA71_BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/02/2011:svnAcer:pnAspire7250:pvrV1.10:rvnAcer:rnHMA71_BZ:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 7250 dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.44-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Tue May 14 13:27:36 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu9 xserver.video_driver: radeon --- .tmp.unity.support.test.0: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.336ubuntu1 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0614] LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115)
[Desktop-packages] [Bug 950415] Re: Chromium Browser takes several attempts to start from launcher
shane, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/950415/comments/5 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/950415 Title: Chromium Browser takes several attempts to start from launcher Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Description: Ubuntu precise (development branch) Release: 12.04 Chromium version: 17.0.963.66~r124982-0ubuntu1 Expected behaviour: I click on the chromium browser launcher icon, the icon pulsates and chromium browser starts up shortly afterwards. What happens instead: I click on the chromium browser launcher icon, the icon pulsates but chromium browser does not start. I click on the launcher icon a second time (after waiting for the icon to stop pulsating) and chromium browser still does not start. I click on the launcher icon a third time and chromium browser starts up shortly afterwards. Additional information: Chromium occasionally starts up first time but this happens maybe 1 in 8-10 attempts. If chromium fails to launch with the first attempt, it sometimes starts up the second time but usually it takes a third attempt. It never takes more than three attempts before finally starting. If I try starting from a terminal, chromium usually starts normally but will occasionally fail to start, with Segmentation fault the only output. This happens in both Unity and Unity 2D. This problem also occurs if using chromium browser from the chromium-daily PPA. The same versions of chromium browser launch normally in Kubuntu/KDE, not tested in other environments. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.997.0~svn20120105r116462-0ubuntu1~ucd1 [origin: LP-PPA-chromium-daily] ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 CrashDB: ubuntu Date: Thu Mar 8 23:39:45 2012 Desktop-Session: DESKTOP_SESSION = ubuntu-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/950415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 944037] Re: Chromium crashes after a few seconds after startup
Norbert Moldován, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/944037 Title: Chromium crashes after a few seconds after startup Status in “chromium-browser” package in Ubuntu: Invalid Bug description: When starting Chromium or Google Chrome it crashes after a few seconds. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 17.0.963.56~r121963-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Thu Mar 1 16:38:48 2012 Desktop-Session: DESKTOP_SESSION = ubuntu-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ DetectedPlugins: (no entry found in the Preferences file) Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/944037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 939366] Re: chromium crashes silently on Ubuntu 12.04
Andrei Emeltchenko, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/939366 Title: chromium crashes silently on Ubuntu 12.04 Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Cannot add details since bug tool does not allow to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/939366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220681] Re: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Inval
In the old version, voices/en/ is a directory: /usr/lib/x86_64-linux-gnu/espeak-data/voices/en/ /usr/lib/x86_64-linux-gnu/espeak-data/voices/en/en /usr/lib/x86_64-linux-gnu/espeak-data/voices/en/en-us (containing en, en-us, etc.), while in the new version it is a plain file: /usr/lib/x86_64-linux-gnu/espeak-data/voices/en /usr/lib/x86_64-linux-gnu/espeak-data/voices/en-us So it looks to me like dpkg sometimes has troubles to replace the old directory with a file? I tried this upgrade in a precise and quantal schroot (one using overlayfs, the other isn't, it's a tarball schroot) as well as just with espeak-data quantal → trusty upgrade on my production system, and on a precise live image. I also tried that upgrade with the old and new dpkg. In no case I could reproduce this bug. As a workaround we might add a preinst script which just rm -r's /usr/lib/x86_64-linux-gnu/espeak-data/voices before the upgrade, but that would actually be wrong in the case that the upgrade fails, and it would not explain why that bug happens in the first place. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to espeak in Ubuntu. https://bugs.launchpad.net/bugs/1220681 Title: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link Status in “espeak” package in Ubuntu: Confirmed Bug description: automated report during do-release-upgrade -s -d relevant log Preparing to replace espeak-data:i386 1.46.02-2ubuntu1 (using .../espeak-data_1.47.11-1_i386.deb) ... Unpacking replacement espeak-data:i386 ... dpkg: error processing /var/cache/apt/archives/espeak-data_1.47.11-1_i386.deb (--unpack): unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link --- ProblemType: Package DistroRelease: Ubuntu 13.10 Package: espeak-data 1.46.02-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CheckboxSubmission: b5c71cdd2e648a5dc8e6dfd1c7c6007f CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Wed Sep 4 13:26:42 2013 Dependencies: DuplicateSignature: package:espeak-data:1.46.02-2ubuntu1:ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami ErrorMessage: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami InstallationDate: Installed on 2011-02-25 (921 days ago) InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True SourcePackage: espeak Title: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami UpgradeStatus: Upgraded to saucy on 2013-09-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/espeak/+bug/1220681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 975016] Re: cairo-surface.c produced in very many applications, a core dump
André Grötschel, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install libcairo2-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** This bug is no longer a duplicate of bug 887850 Assert failures in cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed, after upgrading to Oneiric with unity-2d ** Changed in: cairo (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/975016 Title: cairo-surface.c produced in very many applications, a core dump Status in “cairo” package in Ubuntu: Invalid Bug description: I have not made the error to isolate more precisely, but it happens in combination with SSL. __SOME_APPLICATION__ : /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. zsh: abort (core dumped) __SOME_APPLICATION__ List of Application: chromium, firefox, python tools (e.g. gajim, miro), claws-mail, ... xubuntu 12.04 with all updates to 12:20:00 Apr 06 2012 uname -a: Linux 3.2.0-22-generic #35-Ubuntu SMP Tue Apr 3 18:32:42 UTC 2012 i686 athlon i386 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/975016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 888771] [NEW] chromium-browser FATAL:plugin_service
You have been subscribed to a public bug: mama@zeuza:~$ chromium-browser [2555:2567:112972905896:FATAL:plugin_service.cc(73)] Check failed: false. Plugin loading should happen out-of-process. Abortado ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 17.0.935.0~svn2010r109380-0ubuntu1~ucd1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 CrashDB: ubuntu Date: Thu Nov 10 18:54:09 2011 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug i386 oneiric -- chromium-browser FATAL:plugin_service https://bugs.launchpad.net/bugs/888771 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 891534] Re: Network connection crashes when opening gmail in chromium
Ayest, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux REPLACE-WITH-BUG-NUMBER If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested. For example: kernel-fixed-upstream-v3.13-rc8 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: needs-upstream-testing If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER As well, please remove the tag: needs-upstream-testing Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Package changed: chromium-browser (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: New = Incomplete ** Tags added: needs-kernel-logs needs-upstream-testing -- 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/891534 Title: Network connection crashes when opening gmail in chromium Status in “linux” package in Ubuntu: Incomplete Bug description: Description: Ubuntu 11.10 Release: 11.10 $ apt-cache policy chromium-browser chromium-browser: Installé : 17.0.939.0~svn2015r110052-0ubuntu1~ucd1 Candidat : 17.0.940.0~svn2016r110262-0ubuntu1~ucd1 Table de version : 17.0.940.0~svn2016r110262-0ubuntu1~ucd1 0 500 http://ppa.launchpad.net/chromium-daily/ppa/ubuntu/ oneiric/main i386 Packages *** 17.0.939.0~svn2015r110052-0ubuntu1~ucd1 0 100 /var/lib/dpkg/status 15.0.874.106~r107270-0ubuntu0.11.10.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ oneiric-proposed/universe i386 Packages 14.0.835.202~r103287-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages Chrome Version (from the about:version page):17.0.939.0 (Build de développement 110052 Linux) Is this the most recent version: yes OS + version:Ubuntu 11.10 CPU architecture (32-bit / 64-bit):32-bit Window manager: Unity 2D URLs (if relevant): gmail.com Behavior in Linux Firefox: no problem Behavior in Windows Chrome (if you have access to it): no access What steps will reproduce the problem? 1. Go to address https://mail.google.com/ 2. Use gmail for a few seconds/minutes (varying time) What is the expected result? Should work without problem. What happens instead? The network connection crashes, not only gmail connection, but all my network connection. I should use 'sudo ip link set eth0 down' then 'sudo ip link set eth0 up' to have my connection back. This behaviour is reproductible every time. I have no problem using chromium on other site, even google site. I try to clear cache but it does not solve the problem. Sometimes, the problem arise during the loading of gmail, sometimes it arises after a few minutes. Please provide any additional information below. Attach a screenshot and backtrace if possible. I do not use wifi, but hard link. The problem arise with my both gmail account. No gmail labs activated. $ dpkg -l | grep chromium- ii chromium-browser 17.0.939.0~svn2015r110052-0ubuntu1~ucd1 Chromium browser ii chromium-browser-l10n 17.0.939.0~svn2015r110052-0ubuntu1~ucd1 chromium-browser language packages ii chromium-codecs-ffmpeg 17.0.939.0~svn2015r110052-0ubuntu1~ucd1 Free ffmpeg codecs for the Chromium Browser $ uname -a Linux inf209 3.0.0-13-generic-pae #22-Ubuntu SMP Wed Nov 2 15:17:35 UTC 2011 i686 i686 i386 GNU/Linux $ dmesg [...] [ 900.308584] eth0: hw csum failure. [ 900.308587] Pid: 0, comm: kworker/0:0 Tainted: P 3.0.0-13-generic-pae #22-Ubuntu [ 900.308589] Call Trace: [ 900.308591]
[Desktop-packages] [Bug 949439] Re: chromium-browser crashes on some urls
** This bug is no longer a duplicate of bug 887850 Assert failures in cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed, after upgrading to Oneiric with unity-2d -- 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/949439 Title: chromium-browser crashes on some urls Status in “chromium-browser” package in Ubuntu: Expired Bug description: I tried to use gmail.com by chromium browser using command chromium- browser gmail.com, but this is the output in terminal: chromium-browser gmail.com: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Aborted Some other urls do not crash the browser, though. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 17.0.963.65~r124586-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed Mar 7 23:44:00 2012 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/949439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878380] [NEW] Chromium crashes immediately on opening web page
You have been subscribed to a public bug: Snippet from end of console log: Gkr-Message: secret service operation failed: Couldn't create item: Internal error [4076:4085:4329470383:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon [56:56:4329741221:ERROR:nss_util.cc(397)] Error initializing NSS without a persistent database: libsoftokn3.so: cannot open shared object file: Permission denied Gkr-Message: secret service operation failed: Couldn't set item secret [4076:4085:4329788411:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Aborted Browser functions up until the point when an external page is opened (new tab page works fine). Then immediately crashes and window closes. Ubuntu 11.10 chromium-browser: Installed: 14.0.835.202~r103287-0ubuntu1 Candidate: 14.0.835.202~r103287-0ubuntu1 Version table: *** 14.0.835.202~r103287-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 14.0.835.202~r103287-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 18:50:33 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to oneiric on 2011-10-15 (4 days ago) chromium-default: CHROMIUM_FLAGS= ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug i386 oneiric running-unity -- Chromium crashes immediately on opening web page https://bugs.launchpad.net/bugs/878380 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270555] Re: The Text Entry dialog shows invalid keyboard shortcuts to change layout
** Package changed: indicator-keyboard (Ubuntu) = unity-control-center (Ubuntu) ** No longer affects: indicator-keyboard -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1270555 Title: The Text Entry dialog shows invalid keyboard shortcuts to change layout Status in “unity-control-center” package in Ubuntu: New Bug description: On Ubuntu Trusty: Clicking the Text entry settings on indicator-keyboard opens the Text Entry configuration panel. However, this panel shows two keybindings to switch between keyboard layouts which are unusable in their default setting: - Switch to next source using: Super + Space - Switch to previous source using: Shift + Super + Space Changing the combo to any which doesn't include the Super key works- around the problem. I'm speculating that this happens because Compiz/Unity incercepts the Super key since it is used to manage its shortcuts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1270555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 888771] Re: chromium-browser FATAL:plugin_service
** No longer affects: chromium-browser (Ubuntu) ** Changed in: chromium-browser Importance: Unknown = Undecided ** Changed in: chromium-browser Status: Unknown = New ** Changed in: chromium-browser Remote watch: code.google.com/p/chromium/issues #103788 = None -- 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/888771 Title: chromium-browser FATAL:plugin_service Status in “chromium-browser” package in Ubuntu: Invalid Bug description: mama@zeuza:~$ chromium-browser [2555:2567:112972905896:FATAL:plugin_service.cc(73)] Check failed: false. Plugin loading should happen out-of-process. Abortado ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 17.0.935.0~svn2010r109380-0ubuntu1~ucd1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 CrashDB: ubuntu Date: Thu Nov 10 18:54:09 2011 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/888771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260223] Re: randomly is not possible to enter the password [init: indicator-sync main process ended, respawning ]
Blaming xdg-utils, because following David W McCheyne suggestion seems that something in user or local settings is not set. ** Also affects: xdg-utils Importance: Undecided Status: New ** Description changed: Hallo Sometime happens that I type the password, but nothing is showed in the box and the cursor is locked (not blinking) . Even entering the password and pressing enter won't produce effetcs. Workaround: - Login as Guest and then choose your user from the shutdown menu + -Click the keyboard applet in the top right of the task bar ansd click on language. + or + -Login as Guest and then choose your user from the shutdown menu ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Thu Dec 12 09:28:21 2013 EcryptfsInUse: Yes SourcePackage: unity-greeter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Hallo Sometime happens that I type the password, but nothing is showed in the box and the cursor is locked (not blinking) . Even entering the password and pressing enter won't produce effetcs. Workaround: - -Click the keyboard applet in the top right of the task bar ansd click on language. + -Click the keyboard applet in the top right of the task bar and click on language. or -Login as Guest and then choose your user from the shutdown menu + + This happens randomly but frequently ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Thu Dec 12 09:28:21 2013 EcryptfsInUse: Yes SourcePackage: unity-greeter UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1260223 Title: randomly is not possible to enter the password [init: indicator-sync main process ended, respawning ] Status in Xdg-utils: New Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: Hallo Sometime happens that I type the password, but nothing is showed in the box and the cursor is locked (not blinking) . Even entering the password and pressing enter won't produce effetcs. Workaround: -Click the keyboard applet in the top right of the task bar and click on language. or -Login as Guest and then choose your user from the shutdown menu This happens randomly but frequently ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Thu Dec 12 09:28:21 2013 EcryptfsInUse: Yes SourcePackage: unity-greeter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/1260223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 843868] Re: gwibber-accounts crashed after sending credentials to twitter (gwibber-accounts assert failure)
** This bug is no longer a duplicate of bug 887850 Assert failures in cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed, after upgrading to Oneiric with unity-2d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/843868 Title: gwibber-accounts crashed after sending credentials to twitter (gwibber-accounts assert failure) Status in “gwibber” package in Ubuntu: New Bug description: 1. Ubuntu oneiric (development branch) Release: 11.10 2. gwibber: 3.1.90-0ubuntu1 3. I expect gwibber-accounts not to crash, but to add the authorized (twitter-)account. 4. gwibber-accounts crashed an the account data is lost ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gwibber 3.1.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic i686 NonfreeKernelModules: nvidia Architecture: i386 AssertionMessage: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Zusicherung »status == CAIRO_STATUS_SUCCESS« nicht erfüllt. Date: Wed Sep 7 14:52:24 2011 ExecutablePath: /usr/bin/gwibber-accounts InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110906) InterpreterPath: /usr/bin/python2.7 ProcCmdline: python /usr/bin/gwibber-accounts Signal: 6 SourcePackage: gwibber StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 cairo_surface_set_device_offset () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Zusicherung »status == CAIRO_STATUS_SUCCESS« nicht erfüllt. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/843868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 830144] Re: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUC
** This bug is no longer a duplicate of bug 887850 Assert failures in cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed, after upgrading to Oneiric with unity-2d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/830144 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Status in “gwibber” package in Ubuntu: New Bug description: am using Ubuntu 11.10-A3 and Gwibber is version 3.15 . I was signing in to Facebook for the first time when gwibber crashed ! ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gwibber 3.1.5+r1143-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 AssertionMessage: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Date: Sat Aug 20 18:11:47 2011 ExecutablePath: /usr/bin/gwibber-accounts InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110803.1) InterpreterPath: /usr/bin/python2.7 ProcCmdline: python /usr/bin/gwibber-accounts Signal: 6 SourcePackage: gwibber StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 cairo_surface_set_device_offset () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/830144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 811534] Re: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUC
** This bug is no longer a duplicate of bug 887850 Assert failures in cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed, after upgrading to Oneiric with unity-2d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/811534 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Status in “gwibber” package in Ubuntu: Confirmed Bug description: adding a acount ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gwibber 3.1.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7 Uname: Linux 3.0.0-5-generic i686 Architecture: i386 AssertionMessage: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Date: Sat Jul 16 09:34:19 2011 ExecutablePath: /usr/bin/gwibber-accounts InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110705.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gwibber-accounts ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 Signal: 6 SourcePackage: gwibber StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 cairo_surface_set_device_offset () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. UpgradeStatus: Upgraded to oneiric on 2011-07-13 (2 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/811534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 863406] Re: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUC
** This bug is no longer a duplicate of bug 887850 Assert failures in cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed, after upgrading to Oneiric with unity-2d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/863406 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Status in “gwibber” package in Ubuntu: New Bug description: Everytime I try to add a facebook account to gwibber, it crashes at the facebook authorization screen. It also crashes python. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: i386 AssertionMessage: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Date: Fri Sep 30 11:47:35 2011 ExecutablePath: /usr/bin/gwibber-accounts InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) InterpreterPath: /usr/bin/python2.7 ProcCmdline: python /usr/bin/gwibber-accounts Signal: 6 SourcePackage: gwibber StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 cairo_surface_set_device_offset () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. UpgradeStatus: Upgraded to oneiric on 2011-09-16 (14 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/863406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 859095] Re: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: asserzione \status == CAIRO_STATUS_S
** This bug is no longer a duplicate of bug 887850 Assert failures in cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed, after upgrading to Oneiric with unity-2d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/859095 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: asserzione \status == CAIRO_STATUS_SUCCESS\ non riuscita. Status in “gwibber” package in Ubuntu: Confirmed Bug description: It crashes after i logged in facebook ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gwibber 3.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 AssertionMessage: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: asserzione \status == CAIRO_STATUS_SUCCESS\ non riuscita. CrashCounter: 1 Date: Sun Sep 25 20:43:47 2011 ExecutablePath: /usr/bin/gwibber-accounts InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110904) InterpreterPath: /usr/bin/python2.7 ProcCmdline: python /usr/bin/gwibber-accounts Signal: 6 SourcePackage: gwibber StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 cairo_surface_set_device_offset () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: gwibber-accounts assert failure: python: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: asserzione \status == CAIRO_STATUS_SUCCESS\ non riuscita. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare scanner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/859095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1220681] Re: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Inval
Note that this doesn't seem to affect upgrades from precise: In 1.46.02-0ubuntu1 the files were still in /usr/share/espeak-data/voices/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to espeak in Ubuntu. https://bugs.launchpad.net/bugs/1220681 Title: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link Status in “espeak” package in Ubuntu: Confirmed Bug description: automated report during do-release-upgrade -s -d relevant log Preparing to replace espeak-data:i386 1.46.02-2ubuntu1 (using .../espeak-data_1.47.11-1_i386.deb) ... Unpacking replacement espeak-data:i386 ... dpkg: error processing /var/cache/apt/archives/espeak-data_1.47.11-1_i386.deb (--unpack): unable to move aside `./usr/lib/i386-linux-gnu/espeak-data/voices/en' to install new version: Invalid cross-device link --- ProblemType: Package DistroRelease: Ubuntu 13.10 Package: espeak-data 1.46.02-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CheckboxSubmission: b5c71cdd2e648a5dc8e6dfd1c7c6007f CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Wed Sep 4 13:26:42 2013 Dependencies: DuplicateSignature: package:espeak-data:1.46.02-2ubuntu1:ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami ErrorMessage: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami InstallationDate: Installed on 2011-02-25 (921 days ago) InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True SourcePackage: espeak Title: package espeak-data 1.46.02-2ubuntu1 failed to install/upgrade: ErrorMessage: nie można przenieść ./usr/lib/i386-linux-gnu/espeak-data/voices/en, aby zainstalować nową wersję: Błędne dowiązanie między urządzeniami UpgradeStatus: Upgraded to saucy on 2013-09-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/espeak/+bug/1220681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 888771] Re: chromium-browser FATAL:plugin_service
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New = Confirmed -- 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/888771 Title: chromium-browser FATAL:plugin_service Status in “chromium-browser” package in Ubuntu: Invalid Bug description: mama@zeuza:~$ chromium-browser [2555:2567:112972905896:FATAL:plugin_service.cc(73)] Check failed: false. Plugin loading should happen out-of-process. Abortado ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 17.0.935.0~svn2010r109380-0ubuntu1~ucd1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 CrashDB: ubuntu Date: Thu Nov 10 18:54:09 2011 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/888771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 888771] Re: chromium-browser FATAL:plugin_service
mama21mama, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Project changed: chromium-browser = chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/888771 Title: chromium-browser FATAL:plugin_service Status in “chromium-browser” package in Ubuntu: Invalid Bug description: mama@zeuza:~$ chromium-browser [2555:2567:112972905896:FATAL:plugin_service.cc(73)] Check failed: false. Plugin loading should happen out-of-process. Abortado ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 17.0.935.0~svn2010r109380-0ubuntu1~ucd1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 CrashDB: ubuntu Date: Thu Nov 10 18:54:09 2011 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/888771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885308] Re: Overlay scrollbars crashing Chromium
David Gomes, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/885308 Title: Overlay scrollbars crashing Chromium Status in “chromium-browser” package in Ubuntu: Invalid Bug description: From time to time Chromium crashes and I get the following message using 'dmesg': [ 6317.208840] chromium-browse[1885]: segfault at 200760 ip 7fb2c01ffbab sp 7fffdc962630 error 4 in liboverlay- scrollbar-0.2.so.0.0.11[7fb2c01fb000+f000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/885308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878380] Re: Chromium crashes immediately on opening web page
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New = Confirmed -- 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/878380 Title: Chromium crashes immediately on opening web page Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Snippet from end of console log: Gkr-Message: secret service operation failed: Couldn't create item: Internal error [4076:4085:4329470383:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon [56:56:4329741221:ERROR:nss_util.cc(397)] Error initializing NSS without a persistent database: libsoftokn3.so: cannot open shared object file: Permission denied Gkr-Message: secret service operation failed: Couldn't set item secret [4076:4085:4329788411:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Aborted Browser functions up until the point when an external page is opened (new tab page works fine). Then immediately crashes and window closes. Ubuntu 11.10 chromium-browser: Installed: 14.0.835.202~r103287-0ubuntu1 Candidate: 14.0.835.202~r103287-0ubuntu1 Version table: *** 14.0.835.202~r103287-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 14.0.835.202~r103287-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 18:50:33 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to oneiric on 2011-10-15 (4 days ago) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/878380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878380] Re: Chromium crashes immediately on opening web page
Martin Brook, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Project changed: chromium-browser = chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/878380 Title: Chromium crashes immediately on opening web page Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Snippet from end of console log: Gkr-Message: secret service operation failed: Couldn't create item: Internal error [4076:4085:4329470383:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon [56:56:4329741221:ERROR:nss_util.cc(397)] Error initializing NSS without a persistent database: libsoftokn3.so: cannot open shared object file: Permission denied Gkr-Message: secret service operation failed: Couldn't set item secret [4076:4085:4329788411:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Aborted Browser functions up until the point when an external page is opened (new tab page works fine). Then immediately crashes and window closes. Ubuntu 11.10 chromium-browser: Installed: 14.0.835.202~r103287-0ubuntu1 Candidate: 14.0.835.202~r103287-0ubuntu1 Version table: *** 14.0.835.202~r103287-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 14.0.835.202~r103287-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 18:50:33 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to oneiric on 2011-10-15 (4 days ago) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/878380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878380] Re: Chromium crashes immediately on opening web page
** No longer affects: chromium-browser (Ubuntu) ** Changed in: chromium-browser Importance: Unknown = Undecided ** Changed in: chromium-browser Status: Unknown = New ** Changed in: chromium-browser Remote watch: code.google.com/p/chromium/issues #101160 = None -- 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/878380 Title: Chromium crashes immediately on opening web page Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Snippet from end of console log: Gkr-Message: secret service operation failed: Couldn't create item: Internal error [4076:4085:4329470383:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon [56:56:4329741221:ERROR:nss_util.cc(397)] Error initializing NSS without a persistent database: libsoftokn3.so: cannot open shared object file: Permission denied Gkr-Message: secret service operation failed: Couldn't set item secret [4076:4085:4329788411:ERROR:native_backend_gnome_x.cc(452)] Keyring save failed: Error communicating with gnome-keyring-daemon chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed. Aborted Browser functions up until the point when an external page is opened (new tab page works fine). Then immediately crashes and window closes. Ubuntu 11.10 chromium-browser: Installed: 14.0.835.202~r103287-0ubuntu1 Candidate: 14.0.835.202~r103287-0ubuntu1 Version table: *** 14.0.835.202~r103287-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: chromium-browser 14.0.835.202~r103287-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Wed Oct 19 18:50:33 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to oneiric on 2011-10-15 (4 days ago) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/878380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 886793] Re: Default Plug-in crashed
Kasper Dupont, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/886793 Title: Default Plug-in crashed Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Accessing http://webcache.googleusercontent.com/search?btnG=1pws=0q=cache%3ALWFZEBfoOFEJ%3Almgtfy.com%2F+ caused chromium to report The following plug-in has crashed: Default Plug-in ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: chromium-browser 15.0.874.106~r107270-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19 Uname: Linux 2.6.32-34-generic i686 Architecture: i386 Date: Sun Nov 6 12:49:02 2011 Desktop-Session: DESKTOP_SESSION = gnome-xfwm4 GNOME_DESKTOP_SESSION_ID = this-is-deprecated XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-xfwm4:/etc/xdg XDG_DATA_DIRS = None EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) ProcEnviron: PATH=(custom, user) LANG=en_DK.utf8 SHELL=/bin/bash SourcePackage: chromium-browser chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/886793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 894085] Re: On newly installed Firefox, spell checking is enabled but no language is selected
** Changed in: hundredpapercuts Assignee: Papercuts Ninjas (papercuts-ninja) = (unassigned) ** Changed in: hundredpapercuts Status: New = Triaged ** Changed in: hundredpapercuts Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/894085 Title: On newly installed Firefox, spell checking is enabled but no language is selected Status in One Hundred Papercuts: Triaged Status in “firefox” package in Ubuntu: Triaged Bug description: Test Case Install current daily, using the 11/26 for current test Open FF, go to a page you can type in Type a word, mis-spell it, No spell correction is done Highlight the word, Check spelling is enabled Click on Languages no language will be selected Selecting the language will then start spell checking, language should be slected by default Attaching image in comment 5 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 9.0~b2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0 Uname: Linux 3.1.0-2-generic i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.26-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doug 1448 F pulseaudio BuildID: 2017222449 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 47' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:83847616,10280209,00100201' Controls : 27 Simple ctrls : 18 Channel: beta Date: Wed Nov 23 12:28:22 2011 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (2022) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.102 metric 2 Plugins: QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, Location=/usr/lib/mozilla/plugins DivX® Web Player - Lib=libtotem-mully-plugin.so, Location=/usr/lib/mozilla/plugins Windows Media Player Plug-in 10 (compatible; Totem) - Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins VLC Multimedia Plugin (compatible Totem 3.0.1) - Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=9.0/2017222449 (Running) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Nov 23 11:47:28 doug-XPS-M1330 kernel: [ 2485.996721] nautilus[1455]: segfault at 60 ip 080cc9a7 sp bfbda390 error 4 in nautilus[8048000+169000] Nov 23 11:54:02 doug-XPS-M1330 kernel: [ 2879.788096] CE: hpet increased min_delta_ns to 20113 nsec Nov 23 12:18:44 doug-XPS-M1330 kernel: [ 4362.073947] nautilus[3435]: segfault at 60 ip 080cc9a7 sp bfac3ff0 error 4 in nautilus[8048000+169000] dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/894085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 718935] [NEW] chromium cannot open new sourceforge site
You have been subscribed to a public bug: Binary package hint: chromium-browser The chromium-browser currently available in Maverick seems unable to open the pages of the newest SourceForge.net website. Steps to reproduce: 1. sudo apt-get install chromium-browser 2. $ chromium-browser http://sf.net This affects chromium-browser 9.0.597.94~r73967-0ubuntu0.10.10.1 taken from maverick-updates ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Invalid -- chromium cannot open new sourceforge site https://bugs.launchpad.net/bugs/718935 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 790118] Re: chromium (and also chrome) crashes sometimes (segfault at bbadbeef)
LGB [Gábor Lénárt], thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/790118 Title: chromium (and also chrome) crashes sometimes (segfault at bbadbeef) Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser Though I report this bug against chromium-browser, it seems also google chrome stable and beta (channel) is affected too. It's hard to tell when it happens, it cannot be told that a single URL can trigger this, it seems any URL can trigger, usually it happens some times a day, usually at loading a new tab, but sometimes also when the browser is idle. All of these browsers seems to crash with some common part in the kernel log: segfault at bbadbeef, even on different machines! Please note that (I think) it's not the apparmor related bug, since the browser _usually_ works, just crashing some times a day. The borwser then still works, but all of my tabs shows the Ow, snap usual message. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 13.0.781.0~svn20110529r87210-0ubuntu1~ucd1~natty ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic i686 Architecture: i386 CrashDB: ubuntu Date: Mon May 30 10:11:39 2011 Desktop-Session: DESKTOP_SESSION = gnome-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: Upgraded to natty on 2010-10-20 (221 days ago) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/790118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1227238] Re: Chromium crashes on start in GetDeviceStorageSize string allocation
Kyrill, thank you for reporting this and helping make Ubuntu better. However, your crash report is attached. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid ** Attachment removed: This Chromium core dump https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1227238/+attachment/3827569/+files/_usr_lib_chromium-browser_chromium-browser.1000.crash -- 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/1227238 Title: Chromium crashes on start in GetDeviceStorageSize string allocation Status in “chromium-browser” package in Ubuntu: Invalid Bug description: [13198:13222:0918/202520:ERROR:object_proxy.cc(627)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name [13198:13222:0918/202520:ERROR:object_proxy.cc(627)] Failed to get name owner. Got org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.chromium.Mtpd': no such name terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 28.0.1500.71-0ubuntu1.12.04.1 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Wed Sep 18 20:25:57 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1227238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270794] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1270794/+attachment/3952748/+files/ThreadStacktrace.txt ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1270794/+attachment/3952728/+files/CoreDump.gz ** Changed in: chromium-browser (Ubuntu) Importance: Undecided = Medium ** Tags removed: need-amd64-retrace -- 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/1270794 Title: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Status in “chromium-browser” package in Ubuntu: New Bug description: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** The Chromium browser has been crashed when I try to write a downloaded file on a NFTS file system device. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AssertionMessage: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Date: Mon Jan 20 10:47:12 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser ExecutableTimestamp: 1386651735 InstallationDate: Installed on 2013-07-13 (190 days ago) InstallationMedia: Ubuntu 13.04 - Release amd64 (20130428) MarkForUpload: True ProcCmdline: chromium-browser ProcCwd: /home/neptune2 Signal: 6 SourcePackage: chromium-browser StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f133bc0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x7f1352d5f370, str=0x7f133bc40405 free(): invalid pointer, action=3) at malloc.c:4923 _int_free (av=optimized out, p=0x7f1352d5f360, have_lock=0) at malloc.c:3779 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'elementary-xfce-dark\n'/desktop/gnome/interface/gtk_theme = b'Greybird\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1270794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962202]
Created attachment 92392 Abiword document in AbiWord -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/962202 Title: [Upstream] Support for .abw files in LibreOffice Status in LibreOffice Productivity Suite: Fix Released Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice LibreOffice doesn't open .abw files. Please, improve OO for at least could read abiword docs. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/962202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 834662] Re: vma_stop+0x19/0x40
amias, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/834662 Title: vma_stop+0x19/0x40 Status in “chromium-browser” package in Ubuntu: Invalid Bug description: If i do a google search and click on the first link chromium crashes giving the following in dmesg [50320.559207] BUG: unable to handle kernel paging request at fff3 [50320.559221] IP: [811ab2d9] vma_stop+0x19/0x40 [50320.559238] PGD 1a2c067 PUD 1a2d067 PMD 0 [50320.559249] Oops: [#2] SMP [50320.559256] last sysfs file: /sys/devices/pci:00/:00:1c.3/:06:00.0/net/wlan0/statistics/collisions [50320.559264] CPU 1 [50320.559268] Modules linked in: usbhid hid cryptd aes_x86_64 aes_generic rfcomm binfmt_misc bnep l2cap parport_pc ppdev ipt_MASQUERADE xt_mark iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle ip_tables x_tables nvidia(P) arc4 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm iwlagn snd_seq_midi iwlcore snd_rawmidi snd_seq_midi_event mac80211 joydev snd_seq uvcvideo snd_timer cfg80211 raw1394 snd_seq_device videodev psmouse btusb v4l1_compat v4l2_compat_ioctl32 snd serio_raw bluetooth dell_wmi soundcore snd_page_alloc dell_laptop dcdbas intel_agp lp video parport output ohci1394 sdhci_pci ieee1394 sdhci led_class ahci r8169 mii libahci [50320.559391] [50320.559399] Pid: 18773, comm: chromium-browse Tainted: P D 2.6.35-30-generic #57-Ubuntu /Vostro1710 [50320.559406] RIP: 0010:[811ab2d9] [811ab2d9] vma_stop+0x19/0x40 [50320.559417] RSP: 0018:88012506be38 EFLAGS: 00010213 [50320.559423] RAX: fff3 RBX: 88013ab1b1a0 RCX: 0013 [50320.559429] RDX: 8161e180 RSI: fff3 RDI: 88013ab1b1a0 [50320.559435] RBP: 88012506be48 R08: 00d0 R09: 88013fc3 [50320.559441] R10: 0022 R11: 0293 R12: 880079fd2480 [50320.559447] R13: fff3 R14: 0001 R15: 88012506beb0 [50320.559455] FS: 7f52e8e77920() GS:880001f0() knlGS: [50320.559462] CS: 0010 DS: ES: CR0: 80050033 [50320.559467] CR2: fff3 CR3: 00012cd25000 CR4: 06e0 [50320.559474] DR0: DR1: DR2: [50320.559480] DR3: DR6: 0ff0 DR7: 0400 [50320.559487] Process chromium-browse (pid: 18773, threadinfo 88012506a000, task 8800b16cade0) [50320.559492] Stack: [50320.559495] 0022 88013ab1b1a0 88012506be68 811ab38a [50320.559505] 0 0001 880118071880 88012506bee8 81174260 [50320.559516] 0 fff3 7fff4dc0fe40 8801180718b8 88012506bf48 [50320.559529] Call Trace: [50320.559539] [811ab38a] m_stop+0x1a/0x40
[Desktop-packages] [Bug 962202]
Tested and test file opens. It's empty though, but maybe it is an empty file? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/962202 Title: [Upstream] Support for .abw files in LibreOffice Status in LibreOffice Productivity Suite: Fix Released Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice LibreOffice doesn't open .abw files. Please, improve OO for at least could read abiword docs. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/962202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962202]
Opens fine here with the latest master (although the chart is smaller than in AbiWord). For those who check with 4.2, keep in mind that it's not included in the released version. You should try the latest daily builds, or wait for the next RC. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/962202 Title: [Upstream] Support for .abw files in LibreOffice Status in LibreOffice Productivity Suite: Fix Released Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice LibreOffice doesn't open .abw files. Please, improve OO for at least could read abiword docs. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/962202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 828176] Re: chromium shuts down sporadically
James P. Carter, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/828176 Title: chromium shuts down sporadically Status in “chromium-browser” package in Ubuntu: Invalid Bug description: There seems to be no rhyme or reason to the chromium shutdown. The behavior started approximately 2 weeks ago... to be honest I do not pay much attention to updates and essentially install them over night. I can however state that chromium is affected both on my desktop AMD64 3000 as well as on my virtual running within virtualbox on my macbook air. I ran apport-bug against the version installed in my virtual 12.0.742.112 (90304) Ubuntu 11.04 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 12.0.742.112~r90304-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Wed Aug 17 09:54:01 2011 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/828176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 784376] Re: Session killed when try to resize chromium while watching a ogv file
Paolo Cabaleiro, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/784376 Title: Session killed when try to resize chromium while watching a ogv file Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser While in chromium, when to grab the upper bar to resize, and right while I was pulling the bar down, I got a quick message in a black screen, and my session was closed instantly. Then I went again and try to reproduce the error, and every time it did the same. This happened while watching a OGV video. I will try to append a video later on. lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 apt-cache policy chromium-browser chromium-browser: Instalados: 11.0.696.65~r84435-0ubuntu0.11.04.1 Candidato: 11.0.696.65~r84435-0ubuntu0.11.04.1 Tabla de versión: *** 11.0.696.65~r84435-0ubuntu0.11.04.1 0 500 http://es.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ natty-security/main i386 Packages 100 /var/lib/dpkg/status 10.0.648.205~r81283-0ubuntu1 0 500 http://es.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 11.0.696.65~r84435-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue May 17 23:38:38 2011 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=es_ES:en LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/784376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962202]
(In reply to comment #5) Tested and test file opens. It's empty though, but maybe it is an empty file? It's not. See the attached screenshot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/962202 Title: [Upstream] Support for .abw files in LibreOffice Status in LibreOffice Productivity Suite: Fix Released Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice LibreOffice doesn't open .abw files. Please, improve OO for at least could read abiword docs. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/962202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962202]
Landed in 4.2.0 with http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-4-2-0id=6c5709cc3cb54d8f3b2c6428fb8528c2f1799de1 For more details see: http://fridrich.blogspot.co.il/2014/01/abiword-import-filter-in-libreoffice.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/962202 Title: [Upstream] Support for .abw files in LibreOffice Status in LibreOffice Productivity Suite: Fix Released Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice LibreOffice doesn't open .abw files. Please, improve OO for at least could read abiword docs. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/962202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270794]
StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f133bc0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x7f1352d5f370, str=0x7f133bc40405 free(): invalid pointer, action=3) at malloc.c:4923 _int_free (av=optimized out, p=0x7f1352d5f360, have_lock=0) at malloc.c:3779 gtk_file_system_model_finalize (object=0x7f135296c310) at /build/buildd/gtk+2.0-2.24.17/gtk/gtkfilesystemmodel.c:1003 g_object_unref (_object=0x7f135296c310) at /build/buildd/glib2.0-2.36.0/./gobject/gobject.c:3024 -- 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/1270794 Title: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Status in “chromium-browser” package in Ubuntu: New Bug description: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** The Chromium browser has been crashed when I try to write a downloaded file on a NFTS file system device. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AssertionMessage: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Date: Mon Jan 20 10:47:12 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser ExecutableTimestamp: 1386651735 InstallationDate: Installed on 2013-07-13 (190 days ago) InstallationMedia: Ubuntu 13.04 - Release amd64 (20130428) MarkForUpload: True ProcCmdline: chromium-browser ProcCwd: /home/neptune2 Signal: 6 SourcePackage: chromium-browser StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f133bc0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x7f1352d5f370, str=0x7f133bc40405 free(): invalid pointer, action=3) at malloc.c:4923 _int_free (av=optimized out, p=0x7f1352d5f360, have_lock=0) at malloc.c:3779 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'elementary-xfce-dark\n'/desktop/gnome/interface/gtk_theme = b'Greybird\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1270794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270794] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1270794/+attachment/3952747/+files/StacktraceSource.txt -- 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/1270794 Title: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Status in “chromium-browser” package in Ubuntu: New Bug description: Chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** The Chromium browser has been crashed when I try to write a downloaded file on a NFTS file system device. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.13.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AssertionMessage: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** Date: Mon Jan 20 10:47:12 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser ExecutableTimestamp: 1386651735 InstallationDate: Installed on 2013-07-13 (190 days ago) InstallationMedia: Ubuntu 13.04 - Release amd64 (20130428) MarkForUpload: True ProcCmdline: chromium-browser ProcCwd: /home/neptune2 Signal: 6 SourcePackage: chromium-browser StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f133bc0 *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/unix/sysv/linux/libc_fatal.c:199 malloc_printerr (ptr=0x7f1352d5f370, str=0x7f133bc40405 free(): invalid pointer, action=3) at malloc.c:4923 _int_free (av=optimized out, p=0x7f1352d5f360, have_lock=0) at malloc.c:3779 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: chromium-browser assert failure: *** Error in `chromium-browser': free(): invalid pointer: 0x7f1352d5f370 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'elementary-xfce-dark\n'/desktop/gnome/interface/gtk_theme = b'Greybird\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1270794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 772425] Re: Chromium-browser disappears
Elu, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- 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/772425 Title: Chromium-browser disappears Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser When I understate my chromium-browser, the window disappears. If I click again on the short cut, it stars a new browser, not what i had with my webs open. The window is not lost in other desktop, it is NOWHERE. Description: Ubuntu 11.04 Release: 11.04 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 10.0.648.205~r81283-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 ChromiumPrefs: browser/check_default_browser = **unset** (no such key yet) extensions/settings = (no entry found in the Preferences file) Date: Thu Apr 28 16:32:37 2011 Desktop-Session: DESKTOP_SESSION = gnome XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=es_ES:en LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/772425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 816669] Re: encrypted-home support in new user dialog
** Changed in: hundredpapercuts Status: New = Triaged ** Changed in: hundredpapercuts Assignee: Papercuts Ninjas (papercuts-ninja) = (unassigned) ** Changed in: hundredpapercuts Importance: Undecided = Low -- 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/816669 Title: encrypted-home support in new user dialog Status in One Hundred Papercuts: Triaged Status in “gnome-control-center” package in Ubuntu: Triaged Status in “gnome-control-center” source package in Precise: Triaged Bug description: seb128 asked me to file this bug... He noticed that the Gnome3 new user dialog does not support the encrypt-home-directory feature that was present in previous versions of Gnome. To solve this, the new user dialog would have a boolean checkbox (defaulted to un-checked), which asks if this new user's home directory should be created. Talk to mpt about the wordsmithing. If checked, then you need to add --encrypt-home to the 'adduser' invocation. Before running adduser, you'd also need to ensure that ecryptfs-utils is installed. For real security, you would also need to run (as root) ecryptfs- setup-swap, which would encrypt the user's swap space. This is necessary, as any files/data that gets swapped out to disk could be written in the clear, thereby circumventing the user's requested encryption. Further note that if swap is encrypted, hibernation should be disabled (suspend continues to work just fine). To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/816669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 718107] Re: Segmentation fault when going to sourceforge.net
Rasmus, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal: cd /var/crash sudo rm * ; sudo apt-get update sudo apt-get -y upgrade sudo apt-get -y install chromium-browser-dbg sudo service apport start force_start=1 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: gksudo gedit /etc/apport/crashdb.conf and comment out the line: 'problem_types': ['Bug', 'Package'], by changing it to: # 'problem_types': ['Bug', 'Package'], Save, close, and try to file the crash report again via: ubuntu-bug /var/crash/_my_crash_report.crash I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Invalid -- 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/718107 Title: Segmentation fault when going to sourceforge.net Status in “chromium-browser” package in Ubuntu: Invalid Status in “chromium-browser” package in Debian: Fix Released Bug description: Binary package hint: chromium-browser Steps to reproduce: 1. Go to sourceforge.net What happens?: The site doesn't load, only a white page displays. When looking in /var/log/syslog it shows this error: Feb 13 12:03:44 baerbar kernel: [ 900.290703] chromium-browse[4917]: segfault at 10 ip 7f3c7bb36d67 sp 7fff1afaeb90 error 4 in r600_dri.so[7f3c7bace000+33a000] I've tried to disable all chromium-browser plugins but it didn't help. I've no problem going to sourceforge.net from Firefox. I'm using Chromium 9.0.597.94 (73967) and the 64bit version of Ubuntu 10.10. I'm also using the Ubuntu-X-Swat ppa (don't know if it's related to the error). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: chromium-browser 9.0.597.94~r73967-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 Date: Sun Feb 13 11:53:30 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=da_DK.utf8 SHELL=/bin/bash SourcePackage: chromium-browser chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/718107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
