from:"Donald L Walters"

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

2018-04-25 Thread Donald L Walters

fb keep at it
btu de w9dki / w9gty 40

Sent from my iPhoneX+(beta)

> On Apr 2, 2018, at 23:54, Daniel van Vugt  
> wrote:
> 
> Yeah and that's actually good news.
> 
> I had feared the switch to Xorg by default would mean this bug wouldn't
> happen often enough for us to collect good data in 18.04 (since the
> related apport bug fix last week). But it turns out this will happen
> plenty often enough still.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1748450

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

2018-04-25 Thread Donald L Walters

fb 
I will try todo it in gcc / inline machine language if you can’t find the 
problem if you like

de w9dki / w9gty 40

Sent from my iPhoneX+(beta)


> On Apr 3, 2018, at 00:29, Thomas <1748...@bugs.launchpad.net> wrote:
> 
> Xorg
> 
> 
> 
> Van: boun...@canonical.com  namens Daniel van Vugt 
> 
> Verzonden: dinsdag 3 april 2018 3:52
> Aan: tomlemmen...@hotmail.com
> Onderwerp: [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in 
> _g_log_abort() from g_log_default_handler() from 
> default_log_handler(message="Connection to xwayland lost") from g_logv() from 
> g_log() from 
> 
> This bug is indeed meant to be wayland only. Which duplicates are from
> Xorg?
> 
> Note that the login screen (gdm3) is using wayland by default. So your
> system may report this crash even if you only use Xorg sessions.
> 
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1759788).
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
>

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

2018-04-25 Thread Donald L Walters

fb thx try to fix it...if possible  using cinnamon now and had to shift to a 
macbook pro with homebrew and xcode. slmist a debian (from my dson Derek 
Walters the IphoneX chief engineering team leader
guess who gets the Msc OS “beta” version of new software patches for testing 
...me 藍

btu de w9dki 40

Sent from my iPhoneX+(beta)

> On Apr 2, 2018, at 23:54, Daniel van Vugt  
> wrote:
> 
> Yeah and that's actually good news.
> 
> I had feared the switch to Xorg by default would mean this bug wouldn't
> happen often enough for us to collect good data in 18.04 (since the
> related apport bug fix last week). But it turns out this will happen
> plenty often enough still.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1748450

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

2018-04-25 Thread Donald L Walters

fb thx 73 bk
de w9dki 40

Sent from my iPhone

> On Apr 2, 2018, at 23:22, Jean-Baptiste Lallement 
>  wrote:
> 
> I checked tens of duplicates and all the crashes happen from the login
> screen (XDG_CURRENT_DESKTOP=GNOME-Greeter:GNOME)
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1748450
> 
> Title:
>  gnome-shell crashed with SIGTRAP in _g_log_abort() from
>  g_log_default_handler() from default_log_handler(message="Connection
>  to xwayland lost") from g_logv() from g_log() from 
> 
> Status in gnome-shell package in Ubuntu:
>  Triaged
> 
> Bug description:
>  *** This is a duplicate of bug 1505409, but is being kept separate so
>  as to automatically collect duplicate reports since the stacktrace
>  signature has changed recently. Any resolution and discussion should
>  occur in bug 1505409. ***
> 
>  See also:
>  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
> 
>  ProblemType: Crash
>  DistroRelease: Ubuntu 18.04
>  Package: gnome-shell 3.26.2-0ubuntu2
>  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>  Uname: Linux 4.13.0-33-generic x86_64
>  ApportVersion: 2.20.8-0ubuntu8
>  Architecture: amd64
>  CurrentDesktop: GNOME-Greeter:GNOME
>  Date: Thu Feb  8 23:50:23 2018
>  DisplayManager: gdm3
>  ExecutablePath: /usr/bin/gnome-shell
>  GsettingsChanges:
> 
>  InstallationDate: Installed on 2016-03-21 (690 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
>  ProcCmdline: /usr/bin/gnome-shell
>  ProcEnviron:
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/false
>  Signal: 5
>  SourcePackage: gnome-shell
>  StacktraceTop:
>   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>  Title: gnome-shell crashed with signal 5
>  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>  UserGroups:
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1748450

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  [Impact]

  * Xwayland is failing frequently (not crashing), which triggers a
  crash in gnome-shell because gnome-shell doesn't know how to survive
  after Xwayland has reset itself.

  * The frequent gnome-shell crashes create frequent problem reports and
  annoying dialogs for users, after they log in to an apparently working
  gnome-shell.

  * This affects Xorg sessions too, because the gdm login screen itself
  is a Wayland session. And Xorg users will see the problem dialog after
  they have logged into a Xorg session.

  * The fix simply converts the crash into a silent exit (as decided by
  Gnome upstream). This avoids the mountain of crash reports and
  annoying error dialogs at least. It does not fix the root causes that
  remain in Xwayland, but this is considered acceptable because there
  really isn't a bug in gnome-shell here other than it doesn't know how
  to survive without a connection to Xwayland.

  * For users of Xorg sessions, like bionic default, this is a full fix
  as Xorg users will never get an Xwayland instance after logging in.
  And hence the Xwayland bugs are irrelevant.

  [Test Case]

  * Just install bionic, use it lightly and reboot a few times.

  * Observe crash files are left in /var/crash and problem report
  dialogs after logging in.

  [Regression Potential]

  Medium. The fix does not really change the structure of the existing
  error handling, only changes it from a core dump into a silent exit.
  For Xorg users this should be invisible as the affected login screen
  restarts automatically.

  [Other Info]

  This is a whole class of gnome-shell crash which includes bug 1505409, bug 
1748450 and bug 1556601. All three should be considered the same crash for the 
sake of this SRU. Just don't mark them as duplicates of each other
  because they are all still collecting duplicates of their own.

  -

  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:

[Desktop-packages] [Bug 1388348] [NEW] Firefox Nightly 35.0a1 and Firefox 33.0 will not save page as, in Ubuntu and Xubuntu 14.04

2014-11-01 Thread Donald L Walters

Public bug reported:

Neither Firefox Nightly 35.0a1 or Firefox 33.0 will save a page,
locally.  Clicking File then Save Page As does not do anything in
Ubuntu and Xubuntu 14.10.I have notice this for about the last two
weeks  even before upgrading from Ubuntu and Xubuntu 14.04.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox-trunk 35.0~a1~hg20141004r208732-0ubuntu1~umd1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   walters2337 F...m pulseaudio
 /dev/snd/controlC0:  walters2337 F pulseaudio
 /dev/snd/controlC1:  walters2337 F pulseaudio
BuildID: 20141004131321
Channel: nightly
CurrentDesktop: Unity
Date: Sat Nov  1 03:25:57 2014
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2014-10-26 (5 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
IpRoute:
 default via 192.168.0.1 dev eth0  proto static 
 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.22  metric 1
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=35.0a1/20141004131321 (In use)
RelatedPackageVersions:
 rhythmbox-mozilla 3.0.3-1ubuntu2
 totem-mozilla 3.10.1-1ubuntu6
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 Nov  1 02:33:44 walters-ubuntu kernel: [66781.793766] 
systemd-hostnamed[23610]: Warning: nss-myhostname is not installed. Changing 
the local hostname might make it unresolveable. Please install nss-myhostname!
 Nov  1 03:23:48 walters-ubuntu kernel: [69783.245689] 
systemd-hostnamed[26620]: Warning: nss-myhostname is not installed. Changing 
the local hostname might make it unresolveable. Please install nss-myhostname!
dmi.bios.date: 04/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3207
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8P67
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3207:bd04/13/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug nightly-channel utopic

-- 
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/1388348

Title:
  Firefox Nightly 35.0a1 and Firefox 33.0 will not save page as, in
  Ubuntu and Xubuntu 14.04

Status in “firefox” package in Ubuntu:
  New

Bug description:
  Neither Firefox Nightly 35.0a1 or Firefox 33.0 will save a page,
  locally.  Clicking File then Save Page As does not do anything in
  Ubuntu and Xubuntu 14.10.I have notice this for about the last two
  weeks  even before upgrading from Ubuntu and Xubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: firefox-trunk 35.0~a1~hg20141004r208732-0ubuntu1~umd1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   walters2337 F...m pulseaudio
   /dev/snd/controlC0:  walters2337 F pulseaudio
   /dev/snd/controlC1:  walters2337 F pulseaudio
  BuildID: 20141004131321
  Channel: nightly
  CurrentDesktop: Unity
  Date: Sat Nov  1 03:25:57 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-10-26 (5 days ago)

[Desktop-packages] [Bug 1363340] [NEW] package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package n

2014-08-29 Thread Donald L Walters

Public bug reported:

installed xbuntu beta 1 by mistake, and the system failed to boot
thereafter.

sudo apt-get install ppa-purge
sudo apt-get update
sudo apt-get install --reinstall ubuntu-desktop
sudo apt-get install unity


fail at start up but could get to command line install then

sudo apt-get purge nvidia*

did the trick.  It was nvidis-331 that was the problem with xbunty 14.10
(note!!! 14.10...not 14.04..) that is not a typo.

xxbuntu 14.10 has not been released, but ubuntu 14.10  (BETA 1) has
been... but I was running xbuntu 14.04 to avoit the absolutely
...horrid.. ucuntu 14.04 with its ...deplorable cut paste, and many
other absolutely essential, mouse cut and paste problems

also running gomoe fallback.


I saved evaything (earlier by running from the root command line recovery, 
(with network installed...a must)

sudo apt-get install --reinstall compix*

(this was an  ... unexpected ... one hour load time atn 120 Gbslife
saver)


that absolutely saved me, but also  installed, ubuntu, KDE, xcfe, and... 
xbuntu ..,  no problem  I loved it

now I can choose whichever interface I want, but the computer  boots
only to command line then I have to log on and then

mst type

sudo start gdm

or

sudo start lightdm

**

So far, haven't tried

 sudo start kdm

to start KDE yet from the command line, but I suspect that it will work.


no problem??  I  love command line, and even assembly and machine language.


Remember when all else fails

suto apt-get install  --reinstall compix*

is a last case , end of life, absolute lifesaver, that can work, and has
many fringe benefits

when fixing dsfm from boot and networing fails

before trashing and overwriting the failes

and

sudo apti-get purge Xauthority

etc.   do not work

(though the system still would boot into command line though...and that
is how I survived this  ... self inflicted ... screw up)

and whatever else was wrong withn my profile.


73
W9DKI (google it...and use qrz)
SK

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-opencl-icd-331-updates (not installed)
ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
Uname: Linux 3.16.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
Date: Fri Aug 29 19:14:20 2014
DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also 
in package nvidia-opencl-icd-304 304.123-0ubuntu2
ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-304 304.123-0ubuntu2
InstallationDate: Installed on 2014-08-25 (4 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723)
SourcePackage: nvidia-graphics-drivers-331-updates
Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-304 304.123-0ubuntu2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1363340

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd',
  which is also in package nvidia-opencl-icd-304 304.123-0ubuntu2

Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  New

Bug description:
  installed xbuntu beta 1 by mistake, and the system failed to boot
  thereafter.

  sudo apt-get install ppa-purge
  sudo apt-get update
  sudo apt-get install --reinstall ubuntu-desktop
  sudo apt-get install unity

  
  fail at start up but could get to command line install then

  sudo apt-get purge nvidia*

  did the trick.  It was nvidis-331 that was the problem with xbunty
  14.10  (note!!! 14.10...not 14.04..) that is not a typo.

  xxbuntu 14.10 has not been released, but ubuntu 14.10  (BETA 1)
  has been... but I was running xbuntu 14.04 to avoit the absolutely
  ...horrid.. ucuntu 14.04 with its ...deplorable cut paste, and many
  other absolutely essential, mouse cut and paste problems

  also running gomoe fallback.

  
  I saved evaything (earlier by running from the root command line recovery, 
(with network installed...a must)

  sudo apt-get install --reinstall compix*

  (this was an  ... unexpected ... one hour load time atn 120
  Gbslife saver)

  
  that absolutely saved me, but also  installed, ubuntu, KDE, xcfe, and... 
xbuntu ..,  no problem  I loved it

  now I can choose whichever interface I want, but the computer  boots

[Desktop-packages] [Bug 1363341] [NEW] package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package n

2014-08-29 Thread Donald L Walters

Public bug reported:

installed xbuntu beta 1 by mistake, and the system failed to boot
thereafter.

sudo apt-get install ppa-purge
sudo apt-get update
sudo apt-get install --reinstall ubuntu-desktop
sudo apt-get install unity


fail at start up but could get to command line install then

sudo apt-get purge nvidia*

did the trick.  It was nvidis-331 that was the problem with xbunty 14.10
(note!!! 14.10...not 14.04..) that is not a typo.

xxbuntu 14.10 has not been released, but ubuntu 14.10  (BETA 1) has
been... but I was running xbuntu 14.04 to avoit the absolutely
...horrid.. ucuntu 14.04 with its ...deplorable cut paste, and many
other absolutely essential, mouse cut and paste problems

also running gomoe fallback.


I saved evaything (earlier by running from the root command line recovery, 
(with network installed...a must)

sudo apt-get install --reinstall compix*

(this was an  ... unexpected ... one hour load time atn 120 Gbslife
saver)


that absolutely saved me, but also  installed, ubuntu, KDE, xcfe, and... 
xbuntu ..,  no problem  I loved it

now I can choose whichever interface I want, but the computer  boots
only to command line then I have to log on and then

mst type

sudo start gdm

or

sudo start lightdm

**

So far, haven't tried

 sudo start kdm

to start KDE yet from the command line, but I suspect that it will work.


no problem??  I  love command line, and even assembly and machine language.


Remember when all else fails

suto apt-get install  --reinstall compix*

is a last case , end of life, absolute lifesaver, that can work, and has
many fringe benefits

when fixing dsfm from boot and networing fails

before trashing and overwriting the failes

and

sudo apti-get purge Xauthority

etc.   do not work

(though the system still would boot into command line though...and that
is how I survived this  ... self inflicted ... screw up)

and whatever else was wrong withn my profile.


73
W9DKI (google it...and use qrz)
SK

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-opencl-icd-331-updates (not installed)
ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
Uname: Linux 3.16.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
Date: Fri Aug 29 19:14:20 2014
DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also 
in package nvidia-opencl-icd-304 304.123-0ubuntu2
ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-304 304.123-0ubuntu2
InstallationDate: Installed on 2014-08-25 (4 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723)
SourcePackage: nvidia-graphics-drivers-331-updates
Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-304 304.123-0ubuntu2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1363341

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd',
  which is also in package nvidia-opencl-icd-304 304.123-0ubuntu2

Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  New

Bug description:
  installed xbuntu beta 1 by mistake, and the system failed to boot
  thereafter.

  sudo apt-get install ppa-purge
  sudo apt-get update
  sudo apt-get install --reinstall ubuntu-desktop
  sudo apt-get install unity

  
  fail at start up but could get to command line install then

  sudo apt-get purge nvidia*

  did the trick.  It was nvidis-331 that was the problem with xbunty
  14.10  (note!!! 14.10...not 14.04..) that is not a typo.

  xxbuntu 14.10 has not been released, but ubuntu 14.10  (BETA 1)
  has been... but I was running xbuntu 14.04 to avoit the absolutely
  ...horrid.. ucuntu 14.04 with its ...deplorable cut paste, and many
  other absolutely essential, mouse cut and paste problems

  also running gomoe fallback.

  
  I saved evaything (earlier by running from the root command line recovery, 
(with network installed...a must)

  sudo apt-get install --reinstall compix*

  (this was an  ... unexpected ... one hour load time atn 120
  Gbslife saver)

  
  that absolutely saved me, but also  installed, ubuntu, KDE, xcfe, and... 
xbuntu ..,  no problem  I loved it

  now I can choose whichever interface I want, but the computer  boots

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f

[Desktop-packages] [Bug 1388348] [NEW] Firefox Nightly 35.0a1 and Firefox 33.0 will not save page as, in Ubuntu and Xubuntu 14.04

[Desktop-packages] [Bug 1363340] [NEW] package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package n

[Desktop-packages] [Bug 1363341] [NEW] package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package n

7 matches

Site Navigation

Mail list logo

Footer information