[Desktop-packages] [Bug 1473423] Re: Looking for Xlib when not needing it
** Branch linked: lp:~mardy/signon-ui/lp1473422 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1473423 Title: Looking for Xlib when not needing it Status in signon-ui package in Ubuntu: New Bug description: Signon-ui is looking for x11 library but it requires it only on Qt4 builds, so it should look and #include it only when building Qt4 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1473423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473911] [NEW] Unable to install xserver-xorg-dev
Public bug reported: Невозможно установить пакет xserver-xorg-dev. Требуется для сборки fglrx (Catalyst 15.7). Description:Ubuntu 14.04.2 LTS Release:14.04 Kernel uname -r: 3.16.0-43-generic sudo apt-get install xserver-xorg-dev [sudo] password for user: Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово Некоторые пакеты невозможно установить. Возможно, вы просите невозможного, или же используете нестабильную версию дистрибутива, где запрошенные вами пакеты ещё не созданы или были удалены из Incoming. Следующая информация, возможно, поможет вам: Пакеты, имеющие неудовлетворённые зависимости: unity-control-center : Зависит: libcheese-gtk23 (= 3.4.0) но он не будет установлен Зависит: libcheese7 (= 3.0.1) но он не будет установлен E: Ошибка, pkgProblemResolver::Resolve сгенерировал повреждённые пакеты. Это может быть вызвано отложенными (held) пакетами. При попытке исправить sudo apt-get -f install [sudo] password for user: Чтение списков пакетов… Готово Построение дерева зависимостей Чтение информации о состоянии… Готово обновлено 0, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 0 пакетов не обновлено. == You can not install xserver-xorg-dev. Required to build fglrx (Catalyst 15.7). Description: Ubuntu 14.04.2 LTS Release: 14.04 Kernel uname -r: 3.16.0-43-generic sudo apt-get install xserver-xorg-dev [Sudo] password for user: Reading package lists ... Done Building dependency tree Reading state information ... Done Some packages can not be installed. Perhaps you are asking the impossible, or using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help you: The packages have unmet dependencies: unity-control-center: Depends: libcheese-gtk23 ( = 3.4.0) but it will not be installed Depends: libcheese7 ( = 3.0.1) but it will not be installed E: Error, pkgProblemResolver :: Resolve generated damaged packages. This may be caused by (held) packages. If you try to fix sudo apt-get -f install [Sudo] password for user: Reading package lists ... Done Building dependency tree Reading state information ... Done 0 upgraded, 0 installed new packages, to remove the packages marked 0 and 0 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13 Uname: Linux 3.16.0-43-generic i686 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 13 11:52:21 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.200, 3.16.0-43-generic, i686: installed virtualbox, 4.3.10, 3.16.0-43-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7310] [1002:9809] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1885] InstallationDate: Installed on 2015-07-09 (3 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1) MachineType: Hewlett-Packard HP 655 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-43-generic root=UUID=2e141f71-04b0-4a02-9fd4-5a78fce971fb ro quiet splash SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1885 dmi.board.vendor: Hewlett-Packard dmi.board.version: 66.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.29:bd05/08/2014:svnHewlett-Packard:pnHP655NotebookPC:pvr088412005B10002600010:rvnHewlett-Packard:rn1885:rvr66.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 655 Notebook PC dmi.product.version: 088412005B10002600010 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1441260] Re: weird graphical glitches in 14.10
I suggest closing this, because the PC is out of my physical reach now. If you really want to have (need) that debug info, I can do it for you, otherwise let's close it... Thanks! -- 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/1441260 Title: weird graphical glitches in 14.10 Status in xorg package in Ubuntu: Incomplete Bug description: After performing all upgrades and installing some extra packages (gimp, unattended updates, libreoffice, vino, openssh) and purging some other (gnumeric, abiword) on fresh install I've started suffering strange graphical issues (glitches) - see the attached screenshots. Tomorrow I will try to boot once again from USB the live session to verify it's not hardware-related. As for now... anybody experiencing this? ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 7 18:48:55 2015 InstallationDate: Installed on 2015-04-02 (5 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1441260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473901] [NEW] egl-platform-mir.patch: Incorrect (backwards) pixel formats are accepted
Public bug reported:
egl-platform-mir.patch: Incorrect (backwards) pixel formats are
accepted.
I noticed this recently. GBM reports some pixel formats as supported but
if you use them the colours come out backwards. Turns out it's just our
patch reporting incorrect format support ...
--- a/src/gbm/backends/dri/gbm_dri.c
+++ b/src/gbm/backends/dri/gbm_dri.c
@@ -528,9 +528,11 @@ gbm_dri_is_format_supported(struct gbm_d
switch (format) {
case GBM_BO_FORMAT_XRGB:
case GBM_FORMAT_XRGB:
+ case GBM_FORMAT_XBGR: Wrong. Delete this.
break;
case GBM_BO_FORMAT_ARGB:
case GBM_FORMAT_ARGB:
+ case GBM_FORMAT_ABGR:- Wrong. Delete this
if (usage GBM_BO_USE_SCANOUT)
return 0;
break;
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
egl-platform-mir.patch: Incorrect (backwards) pixel formats are
accepted.
I noticed this recently. GBM reports some pixel formats as supported but
if you use them the colours come out backwards. Turns out it's just our
patch reporting incorrect format support ...
--- a/src/gbm/backends/dri/gbm_dri.c
+++ b/src/gbm/backends/dri/gbm_dri.c
@@ -528,9 +528,11 @@ gbm_dri_is_format_supported(struct gbm_d
- switch (format) {
- case GBM_BO_FORMAT_XRGB:
- case GBM_FORMAT_XRGB:
- + case GBM_FORMAT_XBGR: Wong. Delete
this.
-break;
- case GBM_BO_FORMAT_ARGB:
- case GBM_FORMAT_ARGB:
- + case GBM_FORMAT_ABGR: - Wrong. Delete this
-if (usage GBM_BO_USE_SCANOUT)
- return 0;
-break;
+ switch (format) {
+ case GBM_BO_FORMAT_XRGB:
+ case GBM_FORMAT_XRGB:
+ + case GBM_FORMAT_XBGR: Wrong. Delete this.
+ break;
+ case GBM_BO_FORMAT_ARGB:
+ case GBM_FORMAT_ARGB:
+ + case GBM_FORMAT_ABGR:- Wrong. Delete this
+ if (usage GBM_BO_USE_SCANOUT)
+ return 0;
+ break;
--
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/1473901
Title:
egl-platform-mir.patch: Incorrect (backwards) pixel formats are
accepted
Status in mesa package in Ubuntu:
New
Bug description:
egl-platform-mir.patch: Incorrect (backwards) pixel formats are
accepted.
I noticed this recently. GBM reports some pixel formats as supported
but if you use them the colours come out backwards. Turns out it's
just our patch reporting incorrect format support ...
--- a/src/gbm/backends/dri/gbm_dri.c
+++ b/src/gbm/backends/dri/gbm_dri.c
@@ -528,9 +528,11 @@ gbm_dri_is_format_supported(struct gbm_d
switch (format) {
case GBM_BO_FORMAT_XRGB:
case GBM_FORMAT_XRGB:
+ case GBM_FORMAT_XBGR: Wrong. Delete this.
break;
case GBM_BO_FORMAT_ARGB:
case GBM_FORMAT_ARGB:
+ case GBM_FORMAT_ABGR:- Wrong. Delete this
if (usage GBM_BO_USE_SCANOUT)
return 0;
break;
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1473901/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1367825] Re: Intel i915 video driver causing random crashes on i7 Z77 system
Gareth, have you had issues with Windows on it's own with no VMs? I do not run Windows except for in a VM. If you never have problems running Windows with graphic intensive apps then you can almost be sure the hardware is good. I tried Counter Strike: Source on Linux and it died almost instantly with the same crash as you see. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1367825 Title: Intel i915 video driver causing random crashes on i7 Z77 system Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: (none) Candidate: 2:2.99.910-0ubuntu1.1 System: Shuttle XPC SZ77R5 with 32 GB of memory installed (x4 8GB matched kit of sticks). Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Kernel: 3.13.0-35-generic #62-Ubuntu SMP I am experiencng random lock-ups/crashes when using this system and the i915 video driver is active. This results in a fully corrupted screen and no ability to do anything. The only remedy is to restart the system by holding down the power button. I have tried a number of different ideas from different bug reports but they all seem to be different regarding the i915 driver. The screen corruption can be seen in the attached grab. My last resort to see if it was this driver being responsible was to remove it from the system and make use of the regular vesa drivers. I have been using the vesa driver for a week now with no further crashes. All memory sticks are confirmed as good. I have maxed out the memory running 8 different virtual machines to prove to myself there wasn't a bad stick of memory. Also memtest86+ does not show any faults. This problem has been apparent from kernel 3.2.x right up to not with 3.13.x installed. At various points I did test with kernels from Liquorix to see if the problem was resolved (or in the kernel at all). The crashes have happened in Gnome and KDE with different window managers which suggests it's related to xserver (driver). The crashes can come at any time under any kind of load. Sometimes just scrolling a window or entering some text. The only constant seems to be that something on the screen has to change. If left alone with no interaction the machine would run just fine. I have used it remotely with X forwarding without problem. This definitely seems to be an i915 issue, or something closely related to it. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crispy 3441 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=789ed600-1127-4ac3-9a63-1e8f187636f1 InstallationDate: Installed on 2013-01-06 (612 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SZ77 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/vg-root ro rootdelay=10 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-22 (141 days ago) UserGroups: adm cdrom dip fuse gdm lpadmin plugdev sambashare scanner sudo vboxusers _MarkForUpload: True dmi.bios.date: 05/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.12:bd05/14/2013:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SZ77 dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1367825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1367825] Re: Intel i915 video driver causing random crashes on i7 Z77 system
I've also used the latest drivers from 01.org... https://01.org/linuxgraphics/downloads No dice. Same graphics crash. I am now on 15.04 and the issues persist unless I switch to VESA. Gareth, yes, I believe that using VESA bypasses the GPU. What I find is that the heavier the memory use the more often the crash. If I just browse the web or do simple tasks then the crash doesn't happen as often. However if I spin up several VMs then I can almost predict a crash will happen soon after. I wouldn't say it's like clockwork, but it's generally very quick to come about. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1367825 Title: Intel i915 video driver causing random crashes on i7 Z77 system Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: (none) Candidate: 2:2.99.910-0ubuntu1.1 System: Shuttle XPC SZ77R5 with 32 GB of memory installed (x4 8GB matched kit of sticks). Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Kernel: 3.13.0-35-generic #62-Ubuntu SMP I am experiencng random lock-ups/crashes when using this system and the i915 video driver is active. This results in a fully corrupted screen and no ability to do anything. The only remedy is to restart the system by holding down the power button. I have tried a number of different ideas from different bug reports but they all seem to be different regarding the i915 driver. The screen corruption can be seen in the attached grab. My last resort to see if it was this driver being responsible was to remove it from the system and make use of the regular vesa drivers. I have been using the vesa driver for a week now with no further crashes. All memory sticks are confirmed as good. I have maxed out the memory running 8 different virtual machines to prove to myself there wasn't a bad stick of memory. Also memtest86+ does not show any faults. This problem has been apparent from kernel 3.2.x right up to not with 3.13.x installed. At various points I did test with kernels from Liquorix to see if the problem was resolved (or in the kernel at all). The crashes have happened in Gnome and KDE with different window managers which suggests it's related to xserver (driver). The crashes can come at any time under any kind of load. Sometimes just scrolling a window or entering some text. The only constant seems to be that something on the screen has to change. If left alone with no interaction the machine would run just fine. I have used it remotely with X forwarding without problem. This definitely seems to be an i915 issue, or something closely related to it. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crispy 3441 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=789ed600-1127-4ac3-9a63-1e8f187636f1 InstallationDate: Installed on 2013-01-06 (612 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SZ77 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/vg-root ro rootdelay=10 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-22 (141 days ago) UserGroups: adm cdrom dip fuse gdm lpadmin plugdev sambashare scanner sudo vboxusers _MarkForUpload: True dmi.bios.date: 05/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.12:bd05/14/2013:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SZ77 dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1473422] Re: Platform check in request.cpp should check for ubuntu* platform
** Branch linked: lp:~mardy/signon-ui/lp1473422
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1473422
Title:
Platform check in request.cpp should check for ubuntu* platform
Status in signon-ui package in Ubuntu:
New
Bug description:
In request.cpp around line 318, the code checks if
(QGuiApplication::platformName() != xcb ||
qgetenv(SSOUI_USE_UBUNTU_WEB_VIEW) == QByteArray(1)) {
however it should either also have ... != wayland or have ...
== UbuntuTouchPlatformName
This makes the signon-ui package shipped by ubuntu unusable on non-xcb
platforms as it's build with USE_UBUNTU_WEB_VIEW and so it will
always create UbuntuBrowserRequest rather than BrowserRequest
which is what is wanted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1473422/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473901] Re: egl-platform-mir.patch: Incorrect (backwards) pixel formats are accepted
Linked a loosely related branch, where the bug was first observed.
** Branch linked: lp:~vanvugt/mir/16bpp
--
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/1473901
Title:
egl-platform-mir.patch: Incorrect (backwards) pixel formats are
accepted
Status in mesa package in Ubuntu:
New
Bug description:
egl-platform-mir.patch: Incorrect (backwards) pixel formats are
accepted.
I noticed this recently. GBM reports some pixel formats as supported
but if you use them the colours come out backwards. Turns out it's
just our patch reporting incorrect format support ...
--- a/src/gbm/backends/dri/gbm_dri.c
+++ b/src/gbm/backends/dri/gbm_dri.c
@@ -528,9 +528,11 @@ gbm_dri_is_format_supported(struct gbm_d
switch (format) {
case GBM_BO_FORMAT_XRGB:
case GBM_FORMAT_XRGB:
+ case GBM_FORMAT_XBGR: Wrong. Delete this.
break;
case GBM_BO_FORMAT_ARGB:
case GBM_FORMAT_ARGB:
+ case GBM_FORMAT_ABGR:- Wrong. Delete this
if (usage GBM_BO_USE_SCANOUT)
return 0;
break;
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1473901/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473908] [NEW] Clicking on external links when multiple firefox sessions running no longer works
Public bug reported: I usually have two firefox instances running, started as: firefox -P work firefox -P default --no-remote --new-window Up until the last update (39.0+build5-0ubuntu0.15.04.1) this worked fine. Now, clicking on a link (in, say Thunderbird) gives me the Firefox is already running, but not responding dialog. With just one instance running, clicking on a link still works, so it appears to be a problem with having more than one. Trying the above with -safe-mode has the same problem, so this is not extension-related. $ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 $ apt-cache policy firefox firefox: Installed: 39.0+build5-0ubuntu0.15.04.1 Candidate: 39.0+build5-0ubuntu0.15.04.1 Version table: *** 39.0+build5-0ubuntu0.15.04.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 37.0+build2-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1473908 Title: Clicking on external links when multiple firefox sessions running no longer works Status in firefox package in Ubuntu: New Bug description: I usually have two firefox instances running, started as: firefox -P work firefox -P default --no-remote --new-window Up until the last update (39.0+build5-0ubuntu0.15.04.1) this worked fine. Now, clicking on a link (in, say Thunderbird) gives me the Firefox is already running, but not responding dialog. With just one instance running, clicking on a link still works, so it appears to be a problem with having more than one. Trying the above with -safe-mode has the same problem, so this is not extension-related. $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy firefox firefox: Installed: 39.0+build5-0ubuntu0.15.04.1 Candidate: 39.0+build5-0ubuntu0.15.04.1 Version table: *** 39.0+build5-0ubuntu0.15.04.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 37.0+build2-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1473908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473422] Re: Platform check in request.cpp should check for ubuntu* platform
** Changed in: signon-ui (Ubuntu)
Importance: Undecided = Medium
** Changed in: signon-ui (Ubuntu)
Assignee: (unassigned) = Alberto Mardegan (mardy)
** Changed in: signon-ui (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1473422
Title:
Platform check in request.cpp should check for ubuntu* platform
Status in signon-ui package in Ubuntu:
In Progress
Bug description:
In request.cpp around line 318, the code checks if
(QGuiApplication::platformName() != xcb ||
qgetenv(SSOUI_USE_UBUNTU_WEB_VIEW) == QByteArray(1)) {
however it should either also have ... != wayland or have ...
== UbuntuTouchPlatformName
This makes the signon-ui package shipped by ubuntu unusable on non-xcb
platforms as it's build with USE_UBUNTU_WEB_VIEW and so it will
always create UbuntuBrowserRequest rather than BrowserRequest
which is what is wanted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1473422/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473423] Re: Looking for Xlib when not needing it
** Changed in: signon-ui (Ubuntu) Importance: Undecided = Medium ** Changed in: signon-ui (Ubuntu) Assignee: (unassigned) = Alberto Mardegan (mardy) ** Changed in: signon-ui (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1473423 Title: Looking for Xlib when not needing it Status in signon-ui package in Ubuntu: In Progress Bug description: Signon-ui is looking for x11 library but it requires it only on Qt4 builds, so it should look and #include it only when building Qt4 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1473423/+subscriptions -- Mailing list: https://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 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card
On 31-05-15 13:51:33, Andrey wrote: Affected this bug on Asus Transformer Flip TP500LN Intel HD 4600, Nvidia GeForce 840m, Ubuntu 14.04 x64 sudo prime-select nvidia Error: alternatives are not set up properly Error: nvidia mode can't be enabled Can you attach the output of the following command, please? update-alternatives --display x86_64-linux-gnu_gl_conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1310023 Title: 14.04: Nvidia Prime is unable to switch to the Nvidia card Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: SRU Request On some systems bbswitch requires the skip_optimus_dsm=1 option in order to load properly. So far we have dealt with this problem with system specific quirks based on DMI information. This some times gives us false positives or doesn't cover all systems (it's hard to quirk all systems). We should simply try with and without that option and use whatever works best for the system. This should cover all cases with no need for additional quirks. [Impact] * Loading bbswitch with the wrong option causes the module to fail from loading which, in turn, prevents hybrid graphics from working properly. [Test Case] * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is enabled (attach your /var/log/gpu-manager.log) - Expected: the NVIDIA GPU is enabled. - Bad behavior: the system switches back to the intel driver and the NVIDIA GPU is not used. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A -- I did a fresh install of 14.04 the day it was released. I use a XPS 15z laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia Geforce GT 525M). Booting doesn't work out of the box, but by setting GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 quiet splash in /etc/default/grub it works. acpi=off when installing, removed that from the grub file when installed. I expected that the Prime feature introduced in kernel 3.12 (kernel 3.13.x here) would let me switch between the Intel and Nvidia cards as i like, instead of using Bumblebee, which doesn't work properly with everything. I've installed and tried both the nvidia-331 and nvidia-304 drivers. Exactly the same result from both. Attempting to switch to the Nvidia card in nvidia-settings (tried on almost all of the drivers available, including 331.38) resulted in an error message, in a new window, with no text. prime-switch in terminal gives this output: Segmentation fault (core dumped) Sudoing the process gives no output at all. No graphical performance boost either, still the Intel card... sudo prime-select nvidia gives this output: Error: alternatives are not set up properly Error: nvidia mode can't be enabled I've also tried Bumblebee (not PPA) a few times, but it's also unable to switch. I'm able to use the Intel card temporary, but I would really like to be able to use the full power of my computer... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-prime 0.6.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 20:52:42 2014 InstallationDate: Installed on 2014-04-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1310023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473943] [NEW] root directory inconsistencies in sftp mounts in file manager
Public bug reported: I have a Debian server on 192.168.1.2, and would like to mount its file system root using the File Manager. So I select Connect to Server and enter sftp://root@192.168.1.2 (plus any number of trailing slashes!) The resulting network mount that appears in the Places column calls itself root on 192.168.1.2 (as does the navigation button at the top) and the tool-tip says sftp://192.168.1.2/root;. As might be expected, I cannot navigate below /root (the root user's home directory) to the root of the file system. (I would like to, but I haven't found a way of specifying the Server Address to achieve this.) But now the inconsistency. If I bring up a file open dialogue in another application and click on the identically-named network mount in the Places column, this time it *does* open the file system root, and the navigation button is labelled / on 192.168.1.2. I would expect the File Manager and open file dialogues to display the same point in the remote hierarchy when the mount point is selected - preferably what the open file dialogue does as it is impossible to get to the remote server's file system root in the File Manager. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 13 11:52:15 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-04-24 (445 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - root directory inconsitencies in sftp mounts in file manager + root directory inconsistencies in sftp mounts in file manager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1473943 Title: root directory inconsistencies in sftp mounts in file manager Status in nautilus package in Ubuntu: New Bug description: I have a Debian server on 192.168.1.2, and would like to mount its file system root using the File Manager. So I select Connect to Server and enter sftp://root@192.168.1.2 (plus any number of trailing slashes!) The resulting network mount that appears in the Places column calls itself root on 192.168.1.2 (as does the navigation button at the top) and the tool-tip says sftp://192.168.1.2/root;. As might be expected, I cannot navigate below /root (the root user's home directory) to the root of the file system. (I would like to, but I haven't found a way of specifying the Server Address to achieve this.) But now the inconsistency. If I bring up a file open dialogue in another application and click on the identically-named network mount in the Places column, this time it *does* open the file system root, and the navigation button is labelled / on 192.168.1.2. I would expect the File Manager and open file dialogues to display the same point in the remote hierarchy when the mount point is selected - preferably what the open file dialogue does as it is impossible to get to the remote server's file system root in the File Manager. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 13 11:52:15 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-04-24 (445 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1473943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473828] Re: Update to 1.5.0
** Branch linked: lp:ubuntu/wily-proposed/x11proto-randr ** Branch linked: lp:~ubuntu-branches/ubuntu/wily/libxrandr/wily- proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1473828 Title: Update to 1.5.0 Status in libxrandr package in Ubuntu: Triaged Status in x11proto-randr package in Ubuntu: Triaged Bug description: Update to 1.5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1473828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455060] Re: Ubuntu 12.04 can't print from either cannon or Brother printer backend error, unsupported driver?
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete = Expired -- 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/1455060 Title: Ubuntu 12.04 can't print from either cannon or Brother printer backend error, unsupported driver? Status in cups package in Ubuntu: Expired Bug description: have no idea looks like there is bug 992982 with same issues but to solution listed so I am reporting same problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1455060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473828] Re: Update to 1.5.0
** Branch linked: lp:ubuntu/x11proto-randr -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1473828 Title: Update to 1.5.0 Status in libxrandr package in Ubuntu: Triaged Status in x11proto-randr package in Ubuntu: Fix Released Bug description: Update to 1.5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1473828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474182] Re: Mystery keyring password prompts pop up for no reason
I suspect it is Ubuntu One: Jul 13 17:55:16 hostname org.gnome.keyring.SystemPrompter[1889]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Jul 13 17:55:18 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error $ grep credential error JournalErrors.txt Jul 11 12:49:22 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 11 12:49:22 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 11 12:49:44 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 11 12:49:44 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 12 19:08:56 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 12 19:14:44 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 13 11:34:53 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 13 11:38:02 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 13 17:50:19 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 13 17:55:18 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 13 18:17:27 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 13 18:44:22 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error Jul 13 18:50:08 hostname com.ubuntu.OneConf[1889]: ERROR:oneconf.networksync.ssohandler:credential error These errors would certainly correspond with every few minutes and, if actually accompanied with a dialog box, would be often enough to be insanely frustrating. If there's something to configure in the system settings | Online Accounts, there might be an easy way to fix this; if not, I might be tempted to try apt-get purge account-plugin-ubuntuone and see what happens from there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1474182 Title: Mystery keyring password prompts pop up for no reason Status in gnome-session package in Ubuntu: New Bug description: A prompt box periodically pops up for no apparent reason asking me for my default keyring password.If I click Cancel, it re-appears again after a few minutes. There is absolutely no information about what program is asking or why. Is this a phishing scam?!? I'm marking this as security vulnerability because the mystery prompt is asking for extremely sensitive information which users should not give out without knowing what program will use it. * My homedir is not encrypted * I do use automatic login, but it succeeded and everything works, including network. * My system has slept/resumed a few times (don't know if that's relevant) * I use a wired Ethernet connection, not WiFi (so no password is needed for network access). * I am not running any commands that I know of which use encryption or require access to my private keys. Since I am not doing anything which actually requires my private key, something is asking to unlock the keyring wrongly; Or else a background process (or trojan) is trying to communicate with somebody behind my back, using my private keys. This seems to be new (REGRESSION) as of 15.04, it did not occur before upgrading. The programs I *am* running are: * Firefox * Thunderbird (I typed in it's Master Password previously, and it is working fine) * Terminals * A Java based web app (Interactive Brokers Trader Workstation) /var/log/auth.log contains the following: username: Executing command [USER=root] [TTY=unknown] [CWD=/home/username] [COMMAND=/usr/lib/update-notifier/package-system-locked] bus acquired: org.gnome.keyring.SystemPrompter Gcr: registering prompter bus acquired: org.gnome.keyring.PrivatePrompter Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p22@:1.259 Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p22@:1.259 Gcr: creating new GcrPromptDialog prompt Gcr: automatically selecting secret exchange protocol Gcr: generating public key Gcr: beginning the secret exchange: [sx-aes-1]\npublic=RnT9opj6kZDvJpr8QyIBH4DE/xn3wid1Di7mdEuIgT/GCBA1mLB3VdsldoT6WMdJeD15xlSIvvmAiLLR59dffthvV+cifN3K1WoJhFdBDSiBLmkI4wfGXEnQTmJn7iZfyGWsIVqL5cSgG3AEMGKgY4ORzBARp8TLqjnfnoJB3YSh/gNFVs5OT5pCATNeaDN1mx9LzOCuCSwVDXIIY6uV8sjhBpBvQQCNNEV960L2pZYvGsBYMKeriKxvZAJfiO04\n Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p22@:1.259 acquired name: org.gnome.keyring.SystemPrompter acquired name: org.gnome.keyring.PrivatePrompter Gcr: returned from the PromptReady method on
[Desktop-packages] [Bug 1474003] [NEW] Firefox 39 keeps crashing
Public bug reported: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11 libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12 libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13 libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14 libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15 libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16 libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17 libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18 libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19 libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20 libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21 libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22 libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23 libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24 libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25 libxul.so XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469 26 firefox do_main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:294 27 firefox main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:667 28 libc-2.19.so__libc_start_main /build/buildd/eglibc-2.19/csu/libc-start.c:287 Ø 29libstdc++.so.6.0.19 libstdc++.so.6.0.19@0x2ee4bf 30 firefox _init 31 firefox _GLOBAL__sub_I_SSE.cpp /build/firefox-4CFcvq/firefox-39.0+build5/mozglue/build/SSE.cpp:146 32 @0x7ffe8ecf056f 33 ld-2.19.so _dl_init /build/buildd/eglibc-2.19/elf/dl-init.c:36 34 firefox _GLOBAL__sub_I_SSE.cpp
[Desktop-packages] [Bug 1472097] Re: Failed assertion in compCopyWindow
I think the big difference is connecting to Unity8 as the MIr server. So I'm setting XMir as connecting to Unity8 and then the application connecting to XMir. I think that Unity8 is doing something that the demo server isn't doing. I'm not sure if that's an XMir issue or a Unity8 one. -- 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/1472097 Title: Failed assertion in compCopyWindow Status in xorg-server package in Ubuntu: New Bug description: Ted has run into problems trying to integrate XMir with Unity8. When he starts an app, XMir aborts in compCopyWindow. (Log attached) This seems to be because compCopyWindow has been called before compConfigNotify (which in turn call compReallocPixmap, and set cw-oldx to valid values). This might be an initialisation order problem in XMir. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1472097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
** Description changed: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. - There are many identical reports and seems to be unique for Ubuntu - build. + There are at least 1100 identical reports and they seems to be unique + for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25libxul.so XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469 26firefox do_main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:294 27firefox main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:667 28libc-2.19.so__libc_start_main /build/buildd/eglibc-2.19/csu/libc-start.c:287 - Ø 29 libstdc++.so.6.0.19 libstdc++.so.6.0.19@0x2ee4bf - 30firefox _init + Ø 29 libstdc++.so.6.0.19 libstdc++.so.6.0.19@0x2ee4bf + 30firefox _init 31firefox _GLOBAL__sub_I_SSE.cpp /build/firefox-4CFcvq/firefox-39.0+build5/mozglue/build/SSE.cpp:146
[Desktop-packages] [Bug 1448407] Re: icons size issues in Nautilus
the dnd issue should be fixed with https://launchpad.net/ubuntu/+source /humanity-icon-theme/0.6.9 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1448407 Title: icons size issues in Nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 (right after upgrade) Macbook Pro Retina 15 (menu scaling to 1,62) Nautilus scaling 150% for icons and 66% for lists Icons in Nautilus are displayed properly except for LibreOffice icons which are displayed 200-250%. Previews are displayed same size as LibreOffice icons. MS document files are displayed properly (150%) Dragging a file over a folder previously (14.10) made the folder darker (sometimes changing icon to opened) and the file could be dropped. In 15.04 (Nautilus 3.14.2) the folder icon SHRINKS (to 100%) and cannot be seen under the dragged icon. Would be nice if the old behaviour would be restored. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 11:26:58 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] InstallationDate: Installed on 2013-05-17 (707 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
Any fix for vivid? Tried the sane backend dev ppa, but was getting crash notifications on boot. Have a lide 210. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub Status in sane-backends package in Ubuntu: Fix Committed Status in sane-backends package in Fedora: New Status in sane-backends package in Gentoo Linux: Unknown Bug description: I have a HP Scanject 2100c and a Canoscan LIDE-25 both of which use the Sane plustek backend for comms. My PC only has a USB 3 root hub, when either of these devices are connected, either directly or via an external USB 2 hub, they do not work. In general (although not always), 'scanimage -L' will detect the scanner ok: device `plustek:libusb:001:012' is a Hewlett-Packard Scanjet 2100c flatbed scanner however there is always about a 30s delay before the shell prompt is returned. Scanning always fails however, using the suggested method on the sane HOW-TO page: scanimage -vvv -format pnm outfile.pnm Calling sane_exit is the usual response. By enabling debug on the plustek backend, the response I normally get results in the following: [plustek] Vendor ID=0x03F0, Product ID=0x0505 [plustek] usbio_DetectLM983x [plustek] * could not read version register! [plustek] open failed: -1 [plustek] sane_get_devices (0x7fff0686dbc8, 0) In an effort to try and diagnose this, I've build the latest SANE backends from scratch and tried out the latest libusb none of which has resolved the issue. My original kernel was a 3.5.x, I pushed it up to 3.8.0-30 this also made no difference. My guess based on what I've seen is that this is related to the USB 3 hub. The HP Scanjet worked ok on my old Linux box (a 2.6.27 kernel with USB 2 hub) and I've had the Canon one working (albeit not that reliably) on a Raspberry Pi with a 3.6.11 kernel. The key difference (aside from this being a 64 bit flavour of Linux) is the USB. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libsane 1.0.22-7ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Mon Nov 11 19:41:08 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1459571] Re: Keyboard shortcuts stop working
Have to correct myself in #4 , no luck with only changing ccsm Settings like mentioned. Interesting Information: I ´ve tried to workarround with xbindkeys... directelly after starting xbindkeys, all definded keys are working correctelly, after a while, sometimes after hibernate the keys stop working again (but xbindkeys is still running), if I kill xbindkeys in this stage and restart it, it is working probably again. Dont know if this Information is usefull or not -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1459571 Title: Keyboard shortcuts stop working Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: All the global keyboard shortcuts (volume, media, ctrl+alt+t for terminal etc.) handled by u-s-d stop working somewhat randomly. Restarting u-s-d does not help, the only way to get them back is restarting unity (which roughly equals to restarting the whole session). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-settings-daemon 15.04.1+15.04.20150408-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 28 10:37:03 2015 SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1459571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1448407] Re: icons size issues in Nautilus
Just installed 0.6.9 and sorry, no. It does not fix the huge icons at all. The shrunken folder icons are, as far as I can see, gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1448407 Title: icons size issues in Nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 (right after upgrade) Macbook Pro Retina 15 (menu scaling to 1,62) Nautilus scaling 150% for icons and 66% for lists Icons in Nautilus are displayed properly except for LibreOffice icons which are displayed 200-250%. Previews are displayed same size as LibreOffice icons. MS document files are displayed properly (150%) Dragging a file over a folder previously (14.10) made the folder darker (sometimes changing icon to opened) and the file could be dropped. In 15.04 (Nautilus 3.14.2) the folder icon SHRINKS (to 100%) and cannot be seen under the dragged icon. Would be nice if the old behaviour would be restored. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 11:26:58 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] InstallationDate: Installed on 2013-05-17 (707 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474002] [NEW] media keys not working in wily
Public bug reported:
If I run g-s-d manually:
gnome-settings-daemon --replace
Every time a key is pressed I get this error:
Dropping signal AcceleratorActivated of type (ua{sv}) since the type from the
expected interface is (uuu)
This is caused by https://git.gnome.org/browse/gnome-
shell/commit/?id=2aa4fb02dd9c568038d12fe609252b6934367e76 .
g-s-d needs to be updated.
gnome-shell 3.15.4 or newer requires gnome-settings-daemon 3.15.4 or newer.
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
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/1474002
Title:
media keys not working in wily
Status in gnome-settings-daemon package in Ubuntu:
New
Bug description:
If I run g-s-d manually:
gnome-settings-daemon --replace
Every time a key is pressed I get this error:
Dropping signal AcceleratorActivated of type (ua{sv}) since the type from the
expected interface is (uuu)
This is caused by https://git.gnome.org/browse/gnome-
shell/commit/?id=2aa4fb02dd9c568038d12fe609252b6934367e76 .
g-s-d needs to be updated.
gnome-shell 3.15.4 or newer requires gnome-settings-daemon 3.15.4 or newer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1474002/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473828] Re: Update to 1.5.0
This bug was fixed in the package x11proto-randr - 1.5.0-0ubuntu1 --- x11proto-randr (1.5.0-0ubuntu1) wily; urgency=medium * New upstream release (LP: #1473828) -- Robert Ancell robert.anc...@canonical.com Tue, 14 Jul 2015 14:17:25 +1200 ** Changed in: x11proto-randr (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1473828 Title: Update to 1.5.0 Status in libxrandr package in Ubuntu: Triaged Status in x11proto-randr package in Ubuntu: Fix Released Bug description: Update to 1.5.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrandr/+bug/1473828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
@chrisccoulson AFAICT there is no relation between profile state and crashes. Users tried all kind of workarounds but only using different binaries seems to be helpful. I see something SSE.cpp in stack trace, might this be related to CPU SSEx instructions? Maybe the problem triggered by invalid optimization or CPU errata? Also maybe CPU of builder was fresh enough to trigger usage of optimizations incompatible with older CPU revisions we all use? ** Description changed: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. + + # cat /proc/cpuinfo + processor : 0 + vendor_id : GenuineIntel + cpu family: 6 + model : 42 + model name: Intel(R) Celeron(R) CPU 847 @ 1.10GHz + stepping : 7 + microcode : 0x28 + cpu MHz : 892.546 + cache size: 2048 KB + physical id : 0 + siblings : 2 + core id : 0 + cpu cores : 2 + apicid: 0 + initial apicid: 0 + fpu : yes + fpu_exception : yes + cpuid level : 13 + wp: yes + flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt + bugs : + bogomips : 2195.00 + clflush size : 64 + cache_alignment : 64 + address sizes : 36 bits physical, 48 bits virtual + power management: + Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent
[Desktop-packages] [Bug 1474173] Re: cannot start pulseaudio daemon after adjusting libGL.so.1 settings for skype
This was me listing the same bug with verbose alsa output, instead, before I realized it was pulseaudio. I ended up reinstalling at the time because I got an SSD. I had gotten the same problem after installing skype and going through the same solution, but at the time I didn't realize that skype was the cause. It was marked as answered, but it never was. (I went through that trouble shooting step this time, and it did not fix my issue): https://answers.launchpad.net/ubuntu/+source/alsa- driver/+question/268878 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1474173 Title: cannot start pulseaudio daemon after adjusting libGL.so.1 settings for skype Status in pulseaudio package in Ubuntu: New Bug description: http://askubuntu.com/questions/648069/if-i-fix-skype-according-to- another-au-thread-my-systems-sound-breaks-on-resta Installing skype from the partner repositories. Try to start Skype. It fails. Search online. Found someone else with same error message. Follow instructions in first answer with similar error reported in console. This was what I typed: update-alternatives --display i386-linux-gnu_gl_conf sudo update-alternatives --config i386-linux-gnu_gl_conf (switched to /usr/lib/i386-linux-gnu/mesa/ld.so.conf (option 1) from these options: ` SelectionPathPriority Status 0/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 auto mode * 1/usr/lib/i386-linux-gnu/mesa/ld.so.conf 500 manual mode 2/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 manual mode ` then ran `sudo ldconfig`. Fixes skype issues! Sound works, skype works. Later: Restart computer. Damn. No ability to adjust sound through pulse, only through alsamixer... the sound icon in the top right is greyed out, and system settings sound stuff has no effect... and, on top of that, skype sound is broken for playback, as well (though it does at least start, which is did not do before I used the AU fix listed above). ps aux | grep pulseaudio returns nothing, and pulseaudio -D doesn't work Anyone able to explain what's going on? output from running pulseaudio: E: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64 E: [pulseaudio] module.c: Failed to open module module-bluetooth-policy. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. The bluetooth is a red herring, I have that intentionally disabled on restart. That has not broken the sound before, it wasn't until skype that it broke. noticed that 'additional drivers' had me set to nvidia proprietary driver now, so tried to change that back to X.org Nouveau... That was hard, it wouldn't let me (I would restart and it would be right back on nvidia). Finally it let me be on nouveau. But I had installed and setup bumblebee previously... Maybe that's the source of my problem? But sound used to work on nouveau, even... So frustrating... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1474173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474181] [NEW] Windows slightly moved when using workspace switcher
Public bug reported: When using the workspace switcher, selecting a workspace can slightly move the window below the cursor. This can be quite annoying when using multiple workspaces with two semi-maximized windows each. Switching between the workspaces often moves the window a little bit so it appears in the task switcher of the neighboring workspaces. Steps to reproduce: - open two windows on one workspace - semi-maximize them (i.e. ctrl+super+left/right) - activate workspace switcher - select the workspace while slightly moving the mouse - the window below the cursor has now been slightly moved and appears in the task switcher of neighboring workspaces I realize that this is more of a papercut bug report, but I find it quite noticeable and annoying with my workflow. It might also be less of a problem with other mice, but the touchpad of recent Thinkpads (e.g. X240) often moves the mouse slightly when the touchpad is pressed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jul 13 18:57:50 2015 DistUpgraded: 2015-04-23 15:05:22,518 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X240 [17aa:2214] InstallationDate: Installed on 2014-03-11 (489 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b39a Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20AMA17X00 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-22-generic root=/dev/mapper/system-root ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to vivid on 2015-04-23 (81 days ago) dmi.bios.date: 01/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AMA17X00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET67WW(2.17):bd01/08/2014:svnLENOVO:pn20AMA17X00:pvrThinkPadX240:rvnLENOVO:rn20AMA17X00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AMA17X00 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu Jul 9 15:14:01 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1079 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid ** Attachment added: Screenshot https://bugs.launchpad.net/bugs/1474181/+attachment/4428480/+files/window-moved.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1474181 Title: Windows slightly moved when using workspace switcher Status in compiz package in Ubuntu: New Bug description: When using the workspace switcher, selecting a workspace can slightly move the window below the cursor. This can be quite annoying when using multiple workspaces with two semi-maximized windows each. Switching between the workspaces often moves the window a little bit so it appears in the task switcher of the neighboring workspaces. Steps to reproduce: - open two windows on one workspace - semi-maximize them
[Desktop-packages] [Bug 1474154] Re: Update to 0.1.4
Specifically Debian has dropped the xserver-xspice binary package which I don't know if it is required in Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1474154 Title: Update to 0.1.4 Status in xserver-xorg-video-qxl package in Ubuntu: Triaged Bug description: Update to 0.1.4 by syncing with Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1474154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474182] Re: Mystery keyring password prompts pop up for no reason
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1474182 Title: Mystery keyring password prompts pop up for no reason Status in gnome-session package in Ubuntu: New Bug description: A prompt box periodically pops up for no apparent reason asking me for my default keyring password.If I click Cancel, it re-appears again after a few minutes. There is absolutely no information about what program is asking or why. Is this a phishing scam?!? I'm marking this as security vulnerability because the mystery prompt is asking for extremely sensitive information which users should not give out without knowing what program will use it. * My homedir is not encrypted * I do use automatic login, but it succeeded and everything works, including network. * My system has slept/resumed a few times (don't know if that's relevant) * I use a wired Ethernet connection, not WiFi (so no password is needed for network access). * I am not running any commands that I know of which use encryption or require access to my private keys. Since I am not doing anything which actually requires my private key, something is asking to unlock the keyring wrongly; Or else a background process (or trojan) is trying to communicate with somebody behind my back, using my private keys. This seems to be new (REGRESSION) as of 15.04, it did not occur before upgrading. The programs I *am* running are: * Firefox * Thunderbird (I typed in it's Master Password previously, and it is working fine) * Terminals * A Java based web app (Interactive Brokers Trader Workstation) /var/log/auth.log contains the following: username: Executing command [USER=root] [TTY=unknown] [CWD=/home/username] [COMMAND=/usr/lib/update-notifier/package-system-locked] bus acquired: org.gnome.keyring.SystemPrompter Gcr: registering prompter bus acquired: org.gnome.keyring.PrivatePrompter Gcr: received BeginPrompting call from callback /org/gnome/keyring/Prompt/p22@:1.259 Gcr: preparing a prompt for callback /org/gnome/keyring/Prompt/p22@:1.259 Gcr: creating new GcrPromptDialog prompt Gcr: automatically selecting secret exchange protocol Gcr: generating public key Gcr: beginning the secret exchange: [sx-aes-1]\npublic=RnT9opj6kZDvJpr8QyIBH4DE/xn3wid1Di7mdEuIgT/GCBA1mLB3VdsldoT6WMdJeD15xlSIvvmAiLLR59dffthvV+cifN3K1WoJhFdBDSiBLmkI4wfGXEnQTmJn7iZfyGWsIVqL5cSgG3AEMGKgY4ORzBARp8TLqjnfnoJB3YSh/gNFVs5OT5pCATNeaDN1mx9LzOCuCSwVDXIIY6uV8sjhBpBvQQCNNEV960L2pZYvGsBYMKeriKxvZAJfiO04\n Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p22@:1.259 acquired name: org.gnome.keyring.SystemPrompter acquired name: org.gnome.keyring.PrivatePrompter Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p22@:1.259 Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p22@:1.259 Gcr: receiving secret exchange: [sx-aes-1]\npublic=RL9s/tyPJRw80JDQNBGC+0uQxXfk1uAvJH9XoAULcI4ys/b/Rfz9QNvujXVlhp02Yot7S7K6l5KLBc3i6Ry9SPECjeDm6Y5E4Ry43OmOKjBf7JBUcUvrzfUvwJ87YZ0fYCW8j9nDgrBxt1utCOUDJDHVVANdIK8CMIEXnffiKYjsPq8yjueenqdnM+G8VUoBke8U1Bmc0IHs8elTBBWnoeLQdpnLcpn7k245vO5V4w8Gl3ZZtYrw7t6xxZstRAXR\n Gcr: deriving shared transport key Gcr: deriving transport key Gcr: starting password prompt for callback /org/gnome/keyring/Prompt/p22@:1.259 Gtk: GtkDialog mapped without a transient parent. This is discouraged. Gcr: completed password prompt for callback :1.259@/org/gnome/keyring/Prompt/p22 Gcr: sending the secret exchange: [sx-aes-1]\npublic=RnT9opj6kZDvJpr8QyIBH4DE/xn3wid1Di7mdEuIgT/GCBA1mLB3VdsldoT6WMdJeD15xlSIvvmAiLLR59dffthvV+cifN3K1WoJhFdBDSiBLmkI4wfGXEnQTmJn7iZfyGWsIVqL5cSgG3AEMGKgY4ORzBARp8TLqjnfnoJB3YSh/gNFVs5OT5pCATNeaDN1mx9LzOCuCSwVDXIIY6uV8sjhBpBvQQCNNEV960L2pZYvGsBYMKeriKxvZAJfiO04\n Gcr: calling the PromptReady method on /org/gnome/keyring/Prompt/p22@:1.259 Gcr: returned from the PromptReady method on /org/gnome/keyring/Prompt/p22@:1.259 Gcr: received PerformPrompt call from callback /org/gnome/keyring/Prompt/p22@:1.259 Gcr: stopping prompting for operation /org/gnome/keyring/Prompt/p22@:1.259 Gcr: closing the prompt ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-session-bin 3.14.0-2ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2 Uname: Linux 3.19.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 13 18:56:02 2015 InstallationDate: Installed on 2013-08-06 (707 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1448407] Re: icons size issues in Nautilus
drag and drop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1448407 Title: icons size issues in Nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 (right after upgrade) Macbook Pro Retina 15 (menu scaling to 1,62) Nautilus scaling 150% for icons and 66% for lists Icons in Nautilus are displayed properly except for LibreOffice icons which are displayed 200-250%. Previews are displayed same size as LibreOffice icons. MS document files are displayed properly (150%) Dragging a file over a folder previously (14.10) made the folder darker (sometimes changing icon to opened) and the file could be dropped. In 15.04 (Nautilus 3.14.2) the folder icon SHRINKS (to 100%) and cannot be seen under the dragged icon. Would be nice if the old behaviour would be restored. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 11:26:58 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] InstallationDate: Installed on 2013-05-17 (707 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 181576] Re: Messages flagged as Junk even when junk filtering off (IMAP)
** Changed in: evolution Status: New = Won't Fix -- 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/181576 Title: Messages flagged as Junk even when junk filtering off (IMAP) Status in Evolution: Won't Fix Status in evolution package in Ubuntu: Invalid Bug description: Binary package hint: evolution I have an IMAP account and all the checkboxes for filtering junk are unchecked. The problem is the virtual junk folder continues to get filled with my email. I already have filtering done on my server so I do not want any filtering done at the client. Is there a way to remove the virtual junk folder for IMAP? I wouldn't mind if the mail was visible from both the inbox and the junk folder. I just am tired of having to mark every mail as not junk to get it to show in the inbox. ProblemType: Bug Architecture: i386 Date: Wed Jan 9 11:26:07 2008 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/evolution NonfreeKernelModules: fglrx Package: evolution 2.12.1-0ubuntu1 PackageArchitecture: i386 ProcCmdline: evolution ProcCwd: /home/panthony ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution Uname: Linux msi-pa-1960 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/181576/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1367825] Re: Intel i915 video driver causing random crashes on i7 Z77 system
My main concern now having heard your side of things from a Windows point of view is that this is hardware. I am starting to suspect it might be a power thing... the XPC PSU isn't the highest rated so am starting to think that might be something... hardware outside of the normal XPC items is: * x2 WD Red drives * x4 8GB memory sticks (Patriot in my case) * x1 DVD-RW * Bluetooth USB adaptor * MS Wireless keyboard and mouse (not bluetooth) It could be that adding a video card compound the problem further by adding additional power consumption. All in all not a massive amount, but I am going to work out the total power requirements and research the PSU quality. Would be a shame if that is the cause. Another thing is memory compatibility, maybe the chipset doesn't like the sticks we have, what have you got? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1367825 Title: Intel i915 video driver causing random crashes on i7 Z77 system Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: (none) Candidate: 2:2.99.910-0ubuntu1.1 System: Shuttle XPC SZ77R5 with 32 GB of memory installed (x4 8GB matched kit of sticks). Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Kernel: 3.13.0-35-generic #62-Ubuntu SMP I am experiencng random lock-ups/crashes when using this system and the i915 video driver is active. This results in a fully corrupted screen and no ability to do anything. The only remedy is to restart the system by holding down the power button. I have tried a number of different ideas from different bug reports but they all seem to be different regarding the i915 driver. The screen corruption can be seen in the attached grab. My last resort to see if it was this driver being responsible was to remove it from the system and make use of the regular vesa drivers. I have been using the vesa driver for a week now with no further crashes. All memory sticks are confirmed as good. I have maxed out the memory running 8 different virtual machines to prove to myself there wasn't a bad stick of memory. Also memtest86+ does not show any faults. This problem has been apparent from kernel 3.2.x right up to not with 3.13.x installed. At various points I did test with kernels from Liquorix to see if the problem was resolved (or in the kernel at all). The crashes have happened in Gnome and KDE with different window managers which suggests it's related to xserver (driver). The crashes can come at any time under any kind of load. Sometimes just scrolling a window or entering some text. The only constant seems to be that something on the screen has to change. If left alone with no interaction the machine would run just fine. I have used it remotely with X forwarding without problem. This definitely seems to be an i915 issue, or something closely related to it. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crispy 3441 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=789ed600-1127-4ac3-9a63-1e8f187636f1 InstallationDate: Installed on 2013-01-06 (612 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SZ77 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/vg-root ro rootdelay=10 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-22 (141 days ago) UserGroups: adm cdrom dip fuse gdm lpadmin plugdev sambashare scanner sudo vboxusers _MarkForUpload: True dmi.bios.date: 05/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Desktop-packages] [Bug 1289592] Re: SRU request for bugfix release (debian.tar.gz for trusty provided)
Please upload to trusty-proposed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1289592 Title: SRU request for bugfix release (debian.tar.gz for trusty provided) Status in onboard package in Ubuntu: Fix Released Status in onboard source package in Trusty: New Status in onboard source package in Utopic: New Status in onboard source package in Vivid: Fix Released Bug description: Hi, We have just created a new bugfix micro-release for the version of Onboard shipping with Ubuntu trusty and hope that you will be able to pick it up. IMPACT It contains the following changes compared to the version currently shipping with trusty: onboard (1.0.1-0ubuntu1) trusty; urgency=medium * Request for sponsorship for new upstream release (LP: #1289592) * debian/copyright: - Update and refine copyright section * debian/patches/add_defaults_for_ubuntu.patch: - Add more xembed entries to onboard-defaults.conf * Add initial support for org.gnome.interface scaling-factor 1 (LP #1283491) * Catch Onboard becoming unresponsive due to invisible dialogs * Small fix in the word suggestion line of the layouts * Fix loading of desktop backgrounds with non-ascii filenames * Fix startup failures in case of no defined locale or non-unicode locales * Fix handling of hint file with wrong permissions in /tmp * Fix black bars when xembedding * Ignore x-offset when xembedding in unity-greeter on small screens * Add more entries about embedding to the system defaults example file * Don't activate the move button twice on press * Assume RGBA support exist without compositing only in unity-greeter * Show dialog to enable accessibility also if only word suggestions needs it * Close the language menu when the language button is pressed a second time * Fix back trace and hangs when using click buttons with python3.2 on precise * Work around broken introspection of GLib.filename_from_uri() on precise * Work around jumpy moves and resizes of keyboard after unhiding by auto-show * Update window manager quirk selection after name change in gnome-shell * Fix a GTK depreciation warning * Remove spurious debug output * Some code cleanup * Update translations -- Francesco Fumanti francesco.fuma...@gmx.net Fri, 07 Mar 2014 21:38:09 +0100 TEST CASE - Set scaling-factor 1 and verify that keys are properly sized. Fixes LP: #1283491 - This is a bug-fix micro-release. Install and test for a while to make sure of no regressions. REGRESSION POTENTIAL --- - The update contains a few relatively important fixes. - Apart the ubuntu-desktop and the xubuntu-desktop metapackages, there is no other package depending on it; thus in the worst case of an Onboard breakage, it would be limited to Onboard itself. Thanks in advance for taking the feature freeze exception request into account and feel free to post any questions you might have in this thread. Cheers, Francesco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1289592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1448407] Re: icons size issues in Nautilus
well then ... excellent work :-) what is dnd? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1448407 Title: icons size issues in Nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 (right after upgrade) Macbook Pro Retina 15 (menu scaling to 1,62) Nautilus scaling 150% for icons and 66% for lists Icons in Nautilus are displayed properly except for LibreOffice icons which are displayed 200-250%. Previews are displayed same size as LibreOffice icons. MS document files are displayed properly (150%) Dragging a file over a folder previously (14.10) made the folder darker (sometimes changing icon to opened) and the file could be dropped. In 15.04 (Nautilus 3.14.2) the folder icon SHRINKS (to 100%) and cannot be seen under the dragged icon. Would be nice if the old behaviour would be restored. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 11:26:58 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] InstallationDate: Installed on 2013-05-17 (707 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1367825] Re: Intel i915 video driver causing random crashes on i7 Z77 system
I am sorry I confused things with my VMs comment (I was explaining why I run Windows with 32GB of RAM - I won't make that mistake again). Yes, the problem occurs in Windows without VMs as well. Again my problem is very much like Paul said. I can leave the system for days without a problem. But then when I am reading something something on the screen and decide to move the mouse or scroll down or play a video the system will crash. Though it is crazily inconsistent. I may go a couple of weeks without a crash then have three crashes in an hour. I also thought it was related to memory or a memory issue - the more things I have running the more likely I am to see the problem (e.g. lots of firefox tabs)...but I have let memtest86+ run for hours without it throwing an error. I thought it could be a heat issue because I know I didn't do the greatest job with the thermal paste (I have been watching CPU temperature closely)...but seeing that you and Paul have the same problem I am now more confident that I am OK there. What hardware are you using? Are you using a Shuttle SZ77R5 as well...or something different? Just wanting to rule out a problem with the Shuttle hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1367825 Title: Intel i915 video driver causing random crashes on i7 Z77 system Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: (none) Candidate: 2:2.99.910-0ubuntu1.1 System: Shuttle XPC SZ77R5 with 32 GB of memory installed (x4 8GB matched kit of sticks). Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Kernel: 3.13.0-35-generic #62-Ubuntu SMP I am experiencng random lock-ups/crashes when using this system and the i915 video driver is active. This results in a fully corrupted screen and no ability to do anything. The only remedy is to restart the system by holding down the power button. I have tried a number of different ideas from different bug reports but they all seem to be different regarding the i915 driver. The screen corruption can be seen in the attached grab. My last resort to see if it was this driver being responsible was to remove it from the system and make use of the regular vesa drivers. I have been using the vesa driver for a week now with no further crashes. All memory sticks are confirmed as good. I have maxed out the memory running 8 different virtual machines to prove to myself there wasn't a bad stick of memory. Also memtest86+ does not show any faults. This problem has been apparent from kernel 3.2.x right up to not with 3.13.x installed. At various points I did test with kernels from Liquorix to see if the problem was resolved (or in the kernel at all). The crashes have happened in Gnome and KDE with different window managers which suggests it's related to xserver (driver). The crashes can come at any time under any kind of load. Sometimes just scrolling a window or entering some text. The only constant seems to be that something on the screen has to change. If left alone with no interaction the machine would run just fine. I have used it remotely with X forwarding without problem. This definitely seems to be an i915 issue, or something closely related to it. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crispy 3441 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=789ed600-1127-4ac3-9a63-1e8f187636f1 InstallationDate: Installed on 2013-01-06 (612 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SZ77 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/vg-root ro rootdelay=10 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-22 (141 days ago) UserGroups: adm cdrom dip fuse gdm lpadmin plugdev sambashare scanner sudo vboxusers _MarkForUpload: True dmi.bios.date: 05/14/2013 dmi.bios.vendor: American Megatrends Inc.
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New = Confirmed -- 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/1474003 Title: Firefox 39 keeps crashing Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25libxul.so XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469 26firefox do_main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:294 27firefox main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:667 28libc-2.19.so__libc_start_main /build/buildd/eglibc-2.19/csu/libc-start.c:287 Ø 29
[Desktop-packages] [Bug 1367825] Re: Intel i915 video driver causing random crashes on i7 Z77 system
Yes, exact same Shuttle system. I have also run memtest86+ for a long time. I do find I can reduce the number of crashes when not using VESA by removing one or two sticks of memory, starting to thing it might be power related. Very close to getting a known working AMD card and sticking that in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1367825 Title: Intel i915 video driver causing random crashes on i7 Z77 system Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: (none) Candidate: 2:2.99.910-0ubuntu1.1 System: Shuttle XPC SZ77R5 with 32 GB of memory installed (x4 8GB matched kit of sticks). Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Kernel: 3.13.0-35-generic #62-Ubuntu SMP I am experiencng random lock-ups/crashes when using this system and the i915 video driver is active. This results in a fully corrupted screen and no ability to do anything. The only remedy is to restart the system by holding down the power button. I have tried a number of different ideas from different bug reports but they all seem to be different regarding the i915 driver. The screen corruption can be seen in the attached grab. My last resort to see if it was this driver being responsible was to remove it from the system and make use of the regular vesa drivers. I have been using the vesa driver for a week now with no further crashes. All memory sticks are confirmed as good. I have maxed out the memory running 8 different virtual machines to prove to myself there wasn't a bad stick of memory. Also memtest86+ does not show any faults. This problem has been apparent from kernel 3.2.x right up to not with 3.13.x installed. At various points I did test with kernels from Liquorix to see if the problem was resolved (or in the kernel at all). The crashes have happened in Gnome and KDE with different window managers which suggests it's related to xserver (driver). The crashes can come at any time under any kind of load. Sometimes just scrolling a window or entering some text. The only constant seems to be that something on the screen has to change. If left alone with no interaction the machine would run just fine. I have used it remotely with X forwarding without problem. This definitely seems to be an i915 issue, or something closely related to it. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crispy 3441 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=789ed600-1127-4ac3-9a63-1e8f187636f1 InstallationDate: Installed on 2013-01-06 (612 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SZ77 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/vg-root ro rootdelay=10 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-22 (141 days ago) UserGroups: adm cdrom dip fuse gdm lpadmin plugdev sambashare scanner sudo vboxusers _MarkForUpload: True dmi.bios.date: 05/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.12:bd05/14/2013:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SZ77 dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1367825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1314405] Re: Screen freezes due to Xorg crashed SIGABRT and nouveau error
Hi hugohirsch, Since a moth (July 2015) I am having the same problem. (Up to now everything worked pretty well,...4 years) Randomly the Ubuntu freezes ( no ctr+atl+F1 or ssh) works). completely frozen. Sometimes takes 1 hr sometimes 10 minutes. I am not sure if it is because the graphics driver. I tried, gnome3, unity, firefox and epiphany or even just with a gnome-terminal , I have a steelseries 6GV2 keyboard ( I changed it by the original, but also gets frozen), when playing with the windows suddenly the CPU fan starts to rise its speed and Ubuntu freezes. Sometimes the fan is kept at hogh rate others at low. It happens in a ACER PC intel i5 with nvidia GT 215 [geforce 320][av2] I have ubuntu in a labtop with radeon card and it works well. It is quite annoying. If somebody could help would be fantastic. Regards p.s. From a time to now many people is experiencing such problems. -- 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/1314405 Title: Screen freezes due to Xorg crashed SIGABRT and nouveau error Status in Nouveau Xorg driver: Unknown Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: The machine just freezes in my Unity session, sometimes after minutes, sometimes after some hours. Any audio is running about ten minutes longer before the machine either reboots or Xorg is reloaded. Happens daily since updating to 14.04. I cannot change to different terminals to manually reload Xorg, the machine is blocked once the screen freezes. Trying to report the problem via aport-gtk yields an error upon upload: Apr 29 23:03:08 m whoopsie[1380]: message repeated 3 times: [ offline] Apr 29 23:03:08 m whoopsie[1380]: online Apr 29 23:03:08 m whoopsie[1380]: Parsing /var/crash/_usr_bin_Xorg.0.crash. Apr 29 23:03:09 m whoopsie[1380]: Uploading /var/crash/_usr_bin_Xorg.0.crash. Apr 29 23:05:09 m whoopsie[1380]: Sent; server replied with: No error Apr 29 23:05:09 m whoopsie[1380]: Response code: 502 Apr 29 23:05:09 m whoopsie[1380]: Server replied with: Apr 29 23:05:09 m whoopsie[1380]: htmlbodyh1502 Bad Gateway/h1#012The server returned an invalid or incomplete response.#012/body/html#012 Apr 29 23:05:09 m whoopsie[1380]: Could not upload; processing later (/var/crash/_usr_bin_Xorg.0.crash). Sometimes I do see the aport-UI after logging in to my unity session, but the screen disappears and my unity session is loaded 1 second later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,place,move,imgpng,mousepoll,grid,gnomecompat,unitymtgrabhandles,resize,vpswitch,regex,wall,session,animation,fade,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 29 23:19:46 2014 DistUpgraded: 2014-04-24 15:44:51,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.2.0-61-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Device [10b0:1401] InstallationDate: Installed on 2010-12-04 (1241 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MachineType: Gigabyte Technology Co., Ltd. H55M-USB3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8270ae71-32ed-493b-b740-b52a09b3b4c3 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to trusty on 2014-04-24 (5 days ago) dmi.bios.date: 11/01/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: H55M-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd11/01/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Desktop-packages] [Bug 1459128] Re: metacity no longer honors keybindings without modmask?
please, please, please, revert this! I also noticed this change when going from 1:2.34.13-0ubuntu4 to 1:2.34.13-0ubuntu4.1. For me, the function keys change between workspaces. When some programs, such as an xterm, have the mouse focus, they steal the definitions of the function keys. Other programs, and the background don't. Likewise, after many, many years of using these shortcuts (long predating ubuntu or metacity), my aged brain cannot rewire itself. For the sake of necessity, I tried converting to alt-Fn instead of Fn, but my fingers get confused most of the time, and it seriously affects my workflow. One should definitely be able to assign the Fn keys as desired - user level preferences should always override the app defaults. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1459128 Title: metacity no longer honors keybindings without modmask? Status in metacity package in Ubuntu: New Bug description: I'm extremely attached to the following two keybindings: $ dconf read /org/gnome/desktop/wm/keybindings/raise ['F1'] $ dconf read /org/gnome/desktop/wm/keybindings/lower ['F2'] But they stopped working for me in metacity 2.34.13. (That is, I hit F1/F2 expecting the window under the mouse cursor to be raised/lowered respectively, and it doesn't happen.) When I run `METACITY_VERBOSE=1 METACITY_USE_LOGFILE=1 metacity --replace` and install my keybindings: $ dconf write /org/gnome/desktop/wm/keybindings/raise ['F1'] $ dconf write /org/gnome/desktop/wm/keybindings/lower ['F2'] I notice the following appears in the log file: KEYBINDINGS: Will not grab keybinding F1 without modmask. KEYBINDINGS: Will not grab keybinding F2 without modmask. If I then try installing similar bindings with a modmask: $ dconf write /org/gnome/desktop/wm/keybindings/raise ['ShiftF1'] $ dconf write /org/gnome/desktop/wm/keybindings/lower ['ShiftF2'] no such log message occurs, and the modified keybindings work! When I searched for that log message on the web, it led to this recent commit and bug reference: https://mail.gnome.org/archives/commits-list/2015-April/msg01612.html https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1440570 Note however that this bug seems to refer to VNC, which I am not using. So is it the case that F1/F2, unmodified, can no longer be keyboard shortcuts? This would make me very sad, since I've used them several thousand times per day for the last 25 years or so, and I'm not sure I can rewire my fingers at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1459128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1448407] Re: icons size issues in Nautilus
and sorry, no right, nobody claimed they are, the previous comment state that the dnd issue should be fixed, which you confirmed... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1448407 Title: icons size issues in Nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 (right after upgrade) Macbook Pro Retina 15 (menu scaling to 1,62) Nautilus scaling 150% for icons and 66% for lists Icons in Nautilus are displayed properly except for LibreOffice icons which are displayed 200-250%. Previews are displayed same size as LibreOffice icons. MS document files are displayed properly (150%) Dragging a file over a folder previously (14.10) made the folder darker (sometimes changing icon to opened) and the file could be dropped. In 15.04 (Nautilus 3.14.2) the folder icon SHRINKS (to 100%) and cannot be seen under the dragged icon. Would be nice if the old behaviour would be restored. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 11:26:58 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] InstallationDate: Installed on 2013-05-17 (707 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1350939] Re: Xorg freeze
Hi Christopher, sorry for the delay, but I ended up ditching the netbook, switching to a System76 laptop. It eventually reached the point where I needed something more powerful to work on. I can certainly try booting the machine again and loading on 15.04, but that will take some time. -- 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/1350939 Title: Xorg freeze Status in xorg package in Ubuntu: Expired Bug description: Screen locks up under certain scenarios. May be a red herring but mostly seems to occur: - Running a cpu or memory intensive process (Have 3.5GB RAM, 3.5GB Swap on SSD. Freezes occur even when swap not in use, also has occurred within minutes of booting up) - Shortly after resuming from suspend. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 CurrentDesktop: Unity Date: Thu Jul 31 17:41:43 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3387] InstallationDate: Installed on 2014-06-21 (39 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=UUID=9e1d5d18-566e-4f98-aa85-687f5d45980d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.01 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3387 dmi.board.vendor: Hewlett-Packard dmi.board.version: 36.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.01:bd08/04/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr06971020460320100:rvnHewlett-Packard:rn3387:rvr36.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm1 Notebook PC dmi.product.version: 06971020460320100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jul 31 17:37:51 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1350939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1367825] Re: Intel i915 video driver causing random crashes on i7 Z77 system
I am also thinking of adding in a separate video card hoping that will work around the problem. I would be interested to hear how it works out for you. This is all very frustrating because I got the SZ77R5 due to the fact that it could handle 32GB in the ITX form factor (again so I could load up several VMs on it). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1367825 Title: Intel i915 video driver causing random crashes on i7 Z77 system Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: (none) Candidate: 2:2.99.910-0ubuntu1.1 System: Shuttle XPC SZ77R5 with 32 GB of memory installed (x4 8GB matched kit of sticks). Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Kernel: 3.13.0-35-generic #62-Ubuntu SMP I am experiencng random lock-ups/crashes when using this system and the i915 video driver is active. This results in a fully corrupted screen and no ability to do anything. The only remedy is to restart the system by holding down the power button. I have tried a number of different ideas from different bug reports but they all seem to be different regarding the i915 driver. The screen corruption can be seen in the attached grab. My last resort to see if it was this driver being responsible was to remove it from the system and make use of the regular vesa drivers. I have been using the vesa driver for a week now with no further crashes. All memory sticks are confirmed as good. I have maxed out the memory running 8 different virtual machines to prove to myself there wasn't a bad stick of memory. Also memtest86+ does not show any faults. This problem has been apparent from kernel 3.2.x right up to not with 3.13.x installed. At various points I did test with kernels from Liquorix to see if the problem was resolved (or in the kernel at all). The crashes have happened in Gnome and KDE with different window managers which suggests it's related to xserver (driver). The crashes can come at any time under any kind of load. Sometimes just scrolling a window or entering some text. The only constant seems to be that something on the screen has to change. If left alone with no interaction the machine would run just fine. I have used it remotely with X forwarding without problem. This definitely seems to be an i915 issue, or something closely related to it. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crispy 3441 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=789ed600-1127-4ac3-9a63-1e8f187636f1 InstallationDate: Installed on 2013-01-06 (612 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SZ77 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/vg-root ro rootdelay=10 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-22 (141 days ago) UserGroups: adm cdrom dip fuse gdm lpadmin plugdev sambashare scanner sudo vboxusers _MarkForUpload: True dmi.bios.date: 05/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.12:bd05/14/2013:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SZ77 dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1367825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
Hello, i have the same problem. Deleting ./mozilla or using safe mode didn't help Using firefox 40 (beta) seems to solve this problem -- 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/1474003 Title: Firefox 39 keeps crashing Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25libxul.so XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469 26firefox do_main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:294 27firefox main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:667 28libc-2.19.so__libc_start_main /build/buildd/eglibc-2.19/csu/libc-start.c:287 Ø 29
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
Despite trying at various points throughout the day, I've not been able to make it crash at all. I've been using it on Trusty/x86-64 for the last hour and a half or so and it's not crashed once. There must be something I'm missing here. Have you installed any third party software at all? We had a problem a couple of weeks ago where people were reporting Firefox not starting, and it turned out to be caused by a dodgy Sophos AV update. -- 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/1474003 Title: Firefox 39 keeps crashing Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25libxul.so XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469 26firefox
[Desktop-packages] [Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer-updates (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1470862 Title: When using fglrx module, the virtual consoles are blank and useless Status in fglrx-installer-updates package in Ubuntu: Confirmed Bug description: When the PC boots it shows the sddm login, but if I switch to the first virtual console using Ctrl+Alt+F1, the console is blank. The other consoles are in the same state. Only the virtual console with the sddm login, is running fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: fglrx-updates 2:15.200-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 2 15:31:28 2015 SourcePackage: fglrx-installer-updates UpgradeStatus: Upgraded to vivid on 2015-03-12 (112 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474154] [NEW] Update to 0.1.4
Public bug reported: Update to 0.1.4 by syncing with Debian. ** Affects: xserver-xorg-video-qxl (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version ** Changed in: xserver-xorg-video-qxl (Ubuntu) Status: New = Triaged ** Changed in: xserver-xorg-video-qxl (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1474154 Title: Update to 0.1.4 Status in xserver-xorg-video-qxl package in Ubuntu: Triaged Bug description: Update to 0.1.4 by syncing with Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1474154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
Can confirm this behaviour on Ubuntu 14.04. I'm using Firefox 39 with only one addon (ublock origin) and all plugins either disabled or set to ask for permission to run. Experiencing crashes in both Firefox 39 and Firefox 40 Developer Edition, but Firefox 38 is fine. Playing flashplayer video for 0 - 20 seconds is a guaranteed way to crash Firefox 39, but it also can happen on pages with no flash content and with flashplayer completely disabled. In fact, it can even happen on pages with no HTML content at all (eg. a .png image) -- 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/1474003 Title: Firefox 39 keeps crashing Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25libxul.so XRE_main
[Desktop-packages] [Bug 1319029] Re: Deleting files from desktop freezes machine for short period
Hello, as said by Eric Koegel, it appears that any version of gvfs = 1.23.1 should be fixed. The bug is also mentionned here https://bugzilla.xfce.org/show_bug.cgi?id=10778 I am on gvfs 1.20.3 and did all the update on xubuntu 14.04. Isn't xubuntu 14.04 supposed to have LTS support so to include a higher gvfs version if the current one installed is bugging ? Or are we supposed to do it ourself ? So I hope I post at the right place to ask if gvfs = 1.23.1 could be integrated to xubuntu 14.04. It not always easy to see where to post a request ;) Anyway, have a nice day and thanks for the job you do ! -- 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/1319029 Title: Deleting files from desktop freezes machine for short period Status in gvfs: Unknown Status in xfdesktop: Fix Released Status in gvfs package in Ubuntu: Confirmed Bug description: Notice that this is repeat of old bug report, which was closed without working fix (see #1294209). Deleting files from the desktop directly causes machine to freeze for ~30 seconds, once file is deleted machine responds in a timely manner again. I experience this randomly, about 75% of the times. Old bug report claims it is fixed in version 4.11.5-0ubuntu1 of xfdesktop4, but I still experience this with 4.11.6-1ubuntu1. From ~/.cache/upstart/dbus.log ** (process:1678): WARNING **: *** Unsupported operation detected on trash directory ** (process:1678): WARNING **: A trash files/ directory should only have files linked or unlinked (via moves or deletes). Some other operation has been detected on a file in the directory (eg: a file has been modified). Likely, the data reported by the trash backend will now be inconsistent. ** (process:1678): WARNING **: dir: /home/jussi/.local/share/Trash/files, file: New File.5, type: 1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1319029/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues
After some more testing with mako, one thing I did notice that's a bit odd, is that when the phone is booted with WiFi enabled, only a single default route is created. If I disable WiFi, then re-enable, I see two default routes. This doesn't seem to have any adverse affect on things, but it's worth noting. -- 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/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: In Progress Status in network-manager source package in Vivid: Triaged Bug description: [Impact] NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss. Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric. [Test Case] 1- Connect to a wireless network. 2- Connect to the same network over Ethernet both connections should come up on the same subnet. 3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'. [Regression Potential] Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to. --- With Vivid, having two connections to the same network subnet is unstable due to missing metrics for local networks. Example: Being connected to 192.168.1.0/24 via both wired and wireless will cause connectivity issues as sent packets hop between the two interfaces. It used to be that this wasn't an issue. I would go between work and home and plug in and my machine would automatically connect to wireless and it would use the lower metric ethernet interface for all communications, while the wlan interface would remain connected but unused. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 09:17:27 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-25 (58 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1436330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
I should mention that my crashes have the exact same stacktrace as the one in the posted bug here. If I go to the modules tab in the crash reports viewer, libpulsecommon and libpulse (the pulseaudio libraries) are highlighted in red, as are libgio, libglib, libstdc++, and libpthread. There's no indication of what the red actually means, but I assume it means that the crash involves those assemblies in some way? -- 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/1474003 Title: Firefox 39 keeps crashing Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25libxul.so XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469 26firefox do_main
[Desktop-packages] [Bug 1468786] Re: libgrip FTBFS with newer GTK
This bug was fixed in the package libgrip - 0.3.8+15.10.20150713-0ubuntu1 --- libgrip (0.3.8+15.10.20150713-0ubuntu1) wily; urgency=medium [ Stephen M. Webb ] * replace deprecated GTK functions with non-deprecated GTK 3.16 calls. (LP: #1468786) -- CI Train Bot ci-train-...@canonical.com Mon, 13 Jul 2015 14:44:28 + ** Changed in: libgrip (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgrip in Ubuntu. https://bugs.launchpad.net/bugs/1468786 Title: libgrip FTBFS with newer GTK Status in libgrip: In Progress Status in libgrip package in Ubuntu: Fix Released Status in libgrip package in Debian: Confirmed Bug description: The package fails to build: gesture.c: In function ‘create_window’: gesture.c:219:3: error: ‘gtk_widget_override_background_color’ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkwidget.h:1157) [-Werror=deprecated-declarations] gtk_widget_override_background_color (app-da, GTK_STATE_NORMAL, white); ^ cc1: all warnings being treated as errors An alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libgrip.html affects libgrip assignee bregma status inprogress importance medium To manage notifications about this bug go to: https://bugs.launchpad.net/libgrip/+bug/1468786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1115701] Re: GNOME Printer Setup Tool: HP printers discovered by both usb and hp CUPS backends - Two indistinguishable entries in the list of discovered printers
** Changed in: gnome-control-center Status: Confirmed = Fix Released -- 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/1115701 Title: GNOME Printer Setup Tool: HP printers discovered by both usb and hp CUPS backends - Two indistinguishable entries in the list of discovered printers Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have several HP printers. If I connect one of them via USB and click the + button to add a new printer in GNOME's printer setup tool, I get two entries where a user will not see the difference: HP-LaserJet-3390 HP-LaserJet-3390-2 To find out why I got two entries, I added two print queues, one using the first entry, another using the second entry. Then I ran the command lpstat -v and got device for HP-LaserJet-3390: usb://HP/LaserJet%203390?serial=00CNMJP81545 device for HP-LaserJet-3390-2: hp:/usb/HP_LaserJet_3390?serial=00CNMJP81545 So the first comes from the HP LaserJet 3390 discovered via the usb CUPS backend and the second from the same printer via the hp backend. The preferred backend is the latter, as it is made by HP especially for HP printers. Therefore there should be only one entry, using the hp backend. system-config-printer does this correctly, so usingf the D-Bus service of system-config-printer one should be able to join these entries to one using the hp backend. Note that this is not a duplicate of bug 1115669. That bug is about making duplicate entries distinguishable, this bug is about making the hp backend used with HP printers. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1115701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1468786] Re: libgrip FTBFS with newer GTK
** Branch linked: lp:ubuntu/wily-proposed/libgrip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgrip in Ubuntu. https://bugs.launchpad.net/bugs/1468786 Title: libgrip FTBFS with newer GTK Status in libgrip: In Progress Status in libgrip package in Ubuntu: New Status in libgrip package in Debian: Confirmed Bug description: The package fails to build: gesture.c: In function ‘create_window’: gesture.c:219:3: error: ‘gtk_widget_override_background_color’ is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkwidget.h:1157) [-Werror=deprecated-declarations] gtk_widget_override_background_color (app-da, GTK_STATE_NORMAL, white); ^ cc1: all warnings being treated as errors An alternative build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libgrip.html affects libgrip assignee bregma status inprogress importance medium To manage notifications about this bug go to: https://bugs.launchpad.net/libgrip/+bug/1468786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474003] Re: Firefox 39 keeps crashing
Really annoying. Keeps crashing and crashing. Not usable to surf through the web here. Only two extensions are Adblock Edge and NoScript. Flashplayer and H264 plugins have to be enabled to load. There were no problems until I installed the updates yesterday. -- 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/1474003 Title: Firefox 39 keeps crashing Status in firefox package in Ubuntu: Confirmed Bug description: Firefox 39 keeps crashing after update from Firefox 38. Crashes are random but when idle happens at least once a hour or more frequently when actively used. When replaced with binaries from Mozilla there is no problems at same machine with same profile. There are at least 1100 identical reports and they seems to be unique for Ubuntu build. Below is part of crash report: Crashing Thread Frame Module Signature Source 0 libxul.so mozilla::dom::CrashReporterParent::GenerateChildData /build/firefox-4CFcvq/firefox-39.0+build5/dom/ipc/CrashReporterParent.cpp:114 1 libxul.so mozilla::plugins::PluginModuleChromeParent::ProcessFirstMinidump /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1415 2 libxul.so mozilla::plugins::PluginModuleChromeParent::ActorDestroy /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:1503 3 libxul.so mozilla::plugins::PPluginModuleParent::DestroySubtree /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1588 4 libxul.so mozilla::plugins::PPluginModuleParent::OnChannelError /build/firefox-4CFcvq/firefox-39.0+build5/obj-x86_64-linux-gnu/ipc/ipdl/PPluginModuleParent.cpp:1462 5 libxul.so mozilla::ipc::MessageChannel::NotifyMaybeChannelError /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1622 6 libxul.so mozilla::ipc::MessageChannel::Close /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessageChannel.cpp:1744 7 libxul.so mozilla::plugins::PluginModuleParent::DoShutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2326 8 libxul.so mozilla::plugins::PluginModuleParent::NP_Shutdown /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:2307 9 libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:705 10libxul.so mozilla::plugins::PluginModuleChromeParent::~PluginModuleChromeParent /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/ipc/PluginModuleParent.cpp:741 11libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:237 12libxul.so nsNPAPIPlugin::~nsNPAPIPlugin /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:239 13libxul.so nsNPAPIPlugin::Release /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsNPAPIPlugin.cpp:224 14libxul.so nsPluginHost::Notify /build/firefox-4CFcvq/firefox-39.0+build5/dom/plugins/base/nsPluginHost.cpp:3716 15libxul.so nsTimerImpl::Fire /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:634 16libxul.so nsTimerEvent::Run /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsTimerImpl.cpp:724 17libxul.so nsThread::ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/threads/nsThread.cpp:855 18libxul.so NS_ProcessNextEvent /build/firefox-4CFcvq/firefox-39.0+build5/xpcom/glue/nsThreadUtils.cpp:265 19libxul.so mozilla::ipc::MessagePump::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/glue/MessagePump.cpp:140 20libxul.so MessageLoop::Run /build/firefox-4CFcvq/firefox-39.0+build5/ipc/chromium/src/base/message_loop.cc:226 21libxul.so nsBaseAppShell::Run /build/firefox-4CFcvq/firefox-39.0+build5/widget/nsBaseAppShell.cpp:164 22libxul.so nsAppStartup::Run /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/components/startup/nsAppStartup.cpp:281 23libxul.so XREMain::XRE_mainRun /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4170 24libxul.so XREMain::XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4250 25libxul.so XRE_main /build/firefox-4CFcvq/firefox-39.0+build5/toolkit/xre/nsAppRunner.cpp:4469 26firefox do_main /build/firefox-4CFcvq/firefox-39.0+build5/browser/app/nsBrowserApp.cpp:294 27firefox main
[Desktop-packages] [Bug 1367825] Re: Intel i915 video driver causing random crashes on i7 Z77 system
I can't believe it is power. This is supposed to be a 500W power supply! If it was power you would expect anyone with a video card would be complaining, wouldn't you (a memory stick may take 4 watts vs. potentially 100+ Watts for a video card)? Here is my setup: * x1 256 GB Samsung 840 Pro SATA3 * x1 1TB WD Black SATA3 * x1 DVD-RW * 32GB G.SKILL RIPJAWS DDR3 1600 - mine are on the official compatibility list * Wired keyboard and mouse. Perhaps heat? Perhaps heat can't be dispersed well on the tiny motherboard when all four slots are used? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1367825 Title: Intel i915 video driver causing random crashes on i7 Z77 system Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.1 LTS Release:14.04 apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: (none) Candidate: 2:2.99.910-0ubuntu1.1 System: Shuttle XPC SZ77R5 with 32 GB of memory installed (x4 8GB matched kit of sticks). Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Kernel: 3.13.0-35-generic #62-Ubuntu SMP I am experiencng random lock-ups/crashes when using this system and the i915 video driver is active. This results in a fully corrupted screen and no ability to do anything. The only remedy is to restart the system by holding down the power button. I have tried a number of different ideas from different bug reports but they all seem to be different regarding the i915 driver. The screen corruption can be seen in the attached grab. My last resort to see if it was this driver being responsible was to remove it from the system and make use of the regular vesa drivers. I have been using the vesa driver for a week now with no further crashes. All memory sticks are confirmed as good. I have maxed out the memory running 8 different virtual machines to prove to myself there wasn't a bad stick of memory. Also memtest86+ does not show any faults. This problem has been apparent from kernel 3.2.x right up to not with 3.13.x installed. At various points I did test with kernels from Liquorix to see if the problem was resolved (or in the kernel at all). The crashes have happened in Gnome and KDE with different window managers which suggests it's related to xserver (driver). The crashes can come at any time under any kind of load. Sometimes just scrolling a window or entering some text. The only constant seems to be that something on the screen has to change. If left alone with no interaction the machine would run just fine. I have used it remotely with X forwarding without problem. This definitely seems to be an i915 issue, or something closely related to it. --- ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crispy 3441 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=789ed600-1127-4ac3-9a63-1e8f187636f1 InstallationDate: Installed on 2013-01-06 (612 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: vboxnet0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc. SZ77 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/vg-root ro rootdelay=10 quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-22 (141 days ago) UserGroups: adm cdrom dip fuse gdm lpadmin plugdev sambashare scanner sudo vboxusers _MarkForUpload: True dmi.bios.date: 05/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.12:bd05/14/2013:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: SZ77 dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1474173] Re: cannot start pulseaudio daemon after adjusting libGL.so.1 settings for skype
Have also tried purging pulseaudio from instructions on another ubuntu answer, then reinstalling. Now this is what I see: kajo@kajo-Latitude-E6530:~$ pulseaudio E: [pulseaudio] main.c: Daemon startup without any loaded modules, refusing to work. :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1474173 Title: cannot start pulseaudio daemon after adjusting libGL.so.1 settings for skype Status in pulseaudio package in Ubuntu: New Bug description: http://askubuntu.com/questions/648069/if-i-fix-skype-according-to- another-au-thread-my-systems-sound-breaks-on-resta Installing skype from the partner repositories. Try to start Skype. It fails. Search online. Found someone else with same error message. Follow instructions in first answer with similar error reported in console. This was what I typed: update-alternatives --display i386-linux-gnu_gl_conf sudo update-alternatives --config i386-linux-gnu_gl_conf (switched to /usr/lib/i386-linux-gnu/mesa/ld.so.conf (option 1) from these options: ` SelectionPathPriority Status 0/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 auto mode * 1/usr/lib/i386-linux-gnu/mesa/ld.so.conf 500 manual mode 2/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 manual mode ` then ran `sudo ldconfig`. Fixes skype issues! Sound works, skype works. Later: Restart computer. Damn. No ability to adjust sound through pulse, only through alsamixer... the sound icon in the top right is greyed out, and system settings sound stuff has no effect... and, on top of that, skype sound is broken for playback, as well (though it does at least start, which is did not do before I used the AU fix listed above). ps aux | grep pulseaudio returns nothing, and pulseaudio -D doesn't work Anyone able to explain what's going on? output from running pulseaudio: E: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64 E: [pulseaudio] module.c: Failed to open module module-bluetooth-policy. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. The bluetooth is a red herring, I have that intentionally disabled on restart. That has not broken the sound before, it wasn't until skype that it broke. noticed that 'additional drivers' had me set to nvidia proprietary driver now, so tried to change that back to X.org Nouveau... That was hard, it wouldn't let me (I would restart and it would be right back on nvidia). Finally it let me be on nouveau. But I had installed and setup bumblebee previously... Maybe that's the source of my problem? But sound used to work on nouveau, even... So frustrating... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1474173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1474173] [NEW] cannot start pulseaudio daemon after adjusting libGL.so.1 settings for skype
Public bug reported: http://askubuntu.com/questions/648069/if-i-fix-skype-according-to- another-au-thread-my-systems-sound-breaks-on-resta Installing skype from the partner repositories. Try to start Skype. It fails. Search online. Found someone else with same error message. Follow instructions in first answer with similar error reported in console. This was what I typed: update-alternatives --display i386-linux-gnu_gl_conf sudo update-alternatives --config i386-linux-gnu_gl_conf (switched to /usr/lib/i386-linux-gnu/mesa/ld.so.conf (option 1) from these options: ` SelectionPathPriority Status 0/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 auto mode * 1/usr/lib/i386-linux-gnu/mesa/ld.so.conf 500 manual mode 2/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 manual mode ` then ran `sudo ldconfig`. Fixes skype issues! Sound works, skype works. Later: Restart computer. Damn. No ability to adjust sound through pulse, only through alsamixer... the sound icon in the top right is greyed out, and system settings sound stuff has no effect... and, on top of that, skype sound is broken for playback, as well (though it does at least start, which is did not do before I used the AU fix listed above). ps aux | grep pulseaudio returns nothing, and pulseaudio -D doesn't work Anyone able to explain what's going on? output from running pulseaudio: E: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64 E: [pulseaudio] module.c: Failed to open module module-bluetooth-policy. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. The bluetooth is a red herring, I have that intentionally disabled on restart. That has not broken the sound before, it wasn't until skype that it broke. noticed that 'additional drivers' had me set to nvidia proprietary driver now, so tried to change that back to X.org Nouveau... That was hard, it wouldn't let me (I would restart and it would be right back on nvidia). Finally it let me be on nouveau. But I had installed and setup bumblebee previously... Maybe that's the source of my problem? But sound used to work on nouveau, even... So frustrating... ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1474173 Title: cannot start pulseaudio daemon after adjusting libGL.so.1 settings for skype Status in pulseaudio package in Ubuntu: New Bug description: http://askubuntu.com/questions/648069/if-i-fix-skype-according-to- another-au-thread-my-systems-sound-breaks-on-resta Installing skype from the partner repositories. Try to start Skype. It fails. Search online. Found someone else with same error message. Follow instructions in first answer with similar error reported in console. This was what I typed: update-alternatives --display i386-linux-gnu_gl_conf sudo update-alternatives --config i386-linux-gnu_gl_conf (switched to /usr/lib/i386-linux-gnu/mesa/ld.so.conf (option 1) from these options: ` SelectionPathPriority Status 0/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 auto mode * 1/usr/lib/i386-linux-gnu/mesa/ld.so.conf 500 manual mode 2/usr/lib/nvidia-304-updates/alt_ld.so.conf 9701 manual mode ` then ran `sudo ldconfig`. Fixes skype issues! Sound works, skype works. Later: Restart computer. Damn. No ability to adjust sound through pulse, only through alsamixer... the sound icon in the top right is greyed out, and system settings sound stuff has no effect... and, on top of that, skype sound is broken for playback, as well (though it does at least start, which is did not do before I used the AU fix listed above). ps aux | grep pulseaudio returns nothing, and pulseaudio -D doesn't work Anyone able to explain what's going on? output from running pulseaudio: E: [pulseaudio] ltdl-bind-now.c: Failed to open module /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: /usr/lib/pulse-6.0/modules/module-bluetooth-policy.so: wrong ELF class: ELFCLASS64 E: [pulseaudio] module.c: Failed to open module module-bluetooth-policy. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. The bluetooth is a red herring, I have that intentionally disabled on restart. That has not broken the sound before, it wasn't until skype that it broke. noticed
[Desktop-packages] [Bug 1348384] Re: evince and okular do not render eps files correctly resulting in a black background
Ha ha... we are close to the first birthday of this bug, which is not yet fixed on 15.04 Perhaps it will be fixed for 15.10, or 16.04, or 17.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1348384 Title: evince and okular do not render eps files correctly resulting in a black background Status in evince package in Ubuntu: Invalid Status in libspectre package in Ubuntu: Fix Released Status in okular package in Ubuntu: Invalid Bug description: Several eps files, which previously rendered correctly, are not rendered correctly by evince and okular. It looks as though something is wrong with the transparency setting, since most of the incorrectly-rendered files have a black background, but the figure can somewhat be made out on top of hte black background. The PDF files I have tested are NOT affected. EPS files that were previously viewable correctly ARE affected. Thank you for your time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 24 16:54:06 2014 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-06-03 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1348384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1459235] Re: Google Address book: Unable to open address book
Evolution 3.10.4 Mint 17.2 _x64~ Clean Install. Work around posted as above failed. GOA being uncooperative as in I am unable to add an online account. More work on it coming up. Any forecast on when Evolution will be able to work seamlessly as per past versions with Google? -- 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/1459235 Title: Google Address book: Unable to open address book Status in evolution package in Ubuntu: Confirmed Bug description: Since today (2015-05-27) I've been getting this message when trying to open my Google address book: Unable to open address book This address book cannot be opened. This either means that an incorrect URI was entered, or the server is unreachable. Detailed error message: Unable to connect to 'Google address book': The requested resource was not found: https://developers.google.com/accounts/docs/AuthForInstalledApps Running standard Evolution ( 3.10.4) on Ubuntu 14.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1459235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions
** Changed in: mate-settings-daemon (Ubuntu)
Assignee: (unassigned) = Martin Wimpress (flexiondotorg)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1270579
Title:
On laptops, screen brightness and keyboard backlight isn't memorized
between sessions
Status in Dell Sputnik:
New
Status in One Hundred Papercuts:
Won't Fix
Status in Linux Mint:
Confirmed
Status in upstart :
Confirmed
Status in cinnamon-settings-daemon package in Ubuntu:
Confirmed
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Status in mate-settings-daemon package in Ubuntu:
Confirmed
Status in upower package in Ubuntu:
Confirmed
Status in upstart package in Ubuntu:
Won't Fix
Bug description:
HOW TO REPRODUCE:
1. Boot a laptop.
2. Set a different screen (or keyboard) backlight brightness level.
3. Reboot.
RESULT:
Backlight is not memorized.
FIX:
A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA
sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight
sudo apt-get update
sudo apt-get install sysvinit-backlight
NOTES:
1. If you have installed previous non-deb version, please remove it
carefully manually
sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness
/etc/rc?.d/?25brightness
2. If you have installed previous version from my PPA on Ubuntu 14.04,
please reinstall the package by:
sudo apt-get purge sysvinit-backlight
sudo apt-get install sysvinit-backlight
3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too.
B. Ubuntu 14.10 is near EOL (really in July 2015), so users should upgrade
it to Ubuntu 15.04 (see C below).
My script seems to be incompatible with this Ubuntu version - remove it
with
sudo apt-get purge sysvinit-backlight
sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight
C. Ubuntu 15.04 has systemd-backlight@.service. It saves and restores
screen and keyboard backlight levels.
My script is incompatible with this Ubuntu version.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: initscripts 2.88dsf-41ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic i686
ApportVersion: 2.13.1-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Sun Jan 19 17:20:26 2014
InstallationDate: Installed on 2013-10-20 (91 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
SourcePackage: sysvinit
UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
I am also seeing this on Ubuntu 15.10 with a ThinkPad Wireless Bluetooth Keyboard. Specifically, my ThinkPad keyboard is being detected as a system battery. This is concerning as the system is a Desktop with no battery. Since the wireless keyboard is being detected as a keyboard Power Manager is set to shut the system down when my wireless keyboard power gets low. $ upower --dump Device: /org/freedesktop/UPower/devices/battery_hid_90o7fo61o2co10of4_battery native-path: hid-90:7f:61:2c:10:f4-battery model:ThinkPad Compact Bluetooth Keyboard with TrackPoint power supply: no updated: Mon 13 Jul 2015 01:43:11 AM MDT (14 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 0 Wh energy-empty:0 Wh energy-full: 0 Wh energy-full-design: 0 Wh energy-rate: 0 W percentage: 61%$ upower --dump Device: /org/freedesktop/UPower/devices/battery_hid_90o7fo61o2co10of4_battery native-path: hid-90:7f:61:2c:10:f4-battery model:ThinkPad Compact Bluetooth Keyboard with TrackPoint power supply: no updated: Mon 13 Jul 2015 01:43:11 AM MDT (14 seconds ago) has history: yes has statistics: yes battery887 present: yes rechargeable:yes state: discharging warning-level: none energy: 0 Wh energy-empty:0 Wh energy-full: 0 Wh energy-full-design: 0 Wh energy-rate: 0 W percentage: 61% capacity:100% icon-name: 'battery-full-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Mon 13 Jul 2015 01:29:43 AM MDT (822 seconds ago) has history: no has statistics: no unknown warning-level: none icon-name: '' Daemon: daemon-version: 0.99.2 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep capacity:100% icon-name: 'battery-full-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Mon 13 Jul 2015 01:29:43 AM MDT (822 seconds ago) has history: no has statistics: no unknown warning-level: none icon-name: '' Daemon: daemon-version: 0.99.2 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep $ uname -r 3.19.0-22-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in gnome-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in gnome-power-manager source package in Precise: Invalid Status in upower source package in Precise: Fix Released Status in gnome-power-manager source package in Quantal: Invalid Status in upower source package in Quantal: Won't Fix Status in gnome-power-manager source package in Raring: Invalid Status in upower source package in Raring: Fix Released Status in gnome-power-manager source package in Saucy: Invalid Status in upower source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power
[Desktop-packages] [Bug 1153488] Re: Treats bluetooth input device batteries as batteries
re: comment 64, correction. I meant to state I am running 15.04. I am currently seeing if purging upower will work around the system shutting down if keyboard batter power is low. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1153488 Title: Treats bluetooth input device batteries as batteries Status in gnome-power-manager package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in gnome-power-manager source package in Precise: Invalid Status in upower source package in Precise: Fix Released Status in gnome-power-manager source package in Quantal: Invalid Status in upower source package in Quantal: Won't Fix Status in gnome-power-manager source package in Raring: Invalid Status in upower source package in Raring: Fix Released Status in gnome-power-manager source package in Saucy: Invalid Status in upower source package in Saucy: Fix Released Bug description: [Impact] * There are many Bluetooth devices with battery information inside. When they are treated as system battery, it will make the system poweroff/suspend/hibernate when some Bluetooth device has critical low battery. It is a very annoying behavior for the users. Originally, there is no such Bluetooth battery information until Ubuntu 12.04 brings linux-quantal-lts and linux-raring-lts, so those linux kernels also bring this issue. [Test Case] * Pair some Bluetooth devices, such as Apple Wireless Mouse or Apple Wireless Keyboard. * Click the power indicator and you can find Apple Wireless Mouse is listed as system battery, and there is no Apple Wireless Keyboard. If you open gnome-power-statistics, you can find the 'Supply' field of Apple Wireless Mouse is 'Yes' but it should not be. [Regression Potential] * There is no obvious regression as I know. [Other Info] * Most patches are from upstream, modified to fix the conflicts, and made by the same developer (i.e. fourdollars). * We need another patch from https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d0a934b764c67b4bf626f5b7cf725a6e3066afd2 to make Apple Wireless Keyboard showing. [Original Bug Description] This is a weird one... the system is an HP Pavilion 23 All In One and is powered by a large power supply brick. I currently have an Apple Magic Mouse connected via Bluetooth. As soon as the mouse is connected, the Battery indicator shows up and clicking on that shows that the system is reading my mouse as a battery! See the attached screen shot for what I see in the Power status. Looking at hcitool: ubuntu@201206-11396:~$ hcitool dev Devices: hci0 9C:B7:0D:80:71:DB To make matters even more weird, I actually observed the battery indicator go from full to Critically Low and the system suspended itself. Keep in mind, again, that this system has NO battery, it's reading my bluetooth mouse as a battery device. I disconnected the magic mouse and the battery indicator went to Empty Red outline and status showed Battery Disconnected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Generic [HD-Audio Generic], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1726 F pulseaudio Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb4 irq 16' Mixer name : 'Realtek ALC269VC' Components : 'HDA:10ec0269,103c2aee,00100202' Controls : 21 Simple ctrls : 10 Date: Mon Mar 11 03:54:36 2013 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MachineType: Hewlett-Packard a654 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=e2a5f4ae-dfa2-40be-a6c5-3ddb85dcf68e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1
