[Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[Daniel van Vugt]

Also:

3. Please run 'lspci -k' and attach the output.

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[Daniel van Vugt]

Thanks Tom. More questions:

1. How are you trying to wake up the machine initially? Do you mean you're 
_opening_ the lid and expecting it to wake up (which is correct)?
("If I close the lid, it seems that the computer flat-out doesn't wake up.")

2. Can you please attach output from 'dmesg' ASAP after the problem has
started? I can see some hints of kernel/hardware issues in your
JournalErrors.txt but maybe 'dmesg' would be more useful.

** Description changed:

- It's impossible to make a normal bug report, so here's the best I can
- describe:
- 
- EVERY login to gnome, there is a moment after I enter my password and
- press return, where whole screen goes small-resolution (cursor small,
- all text and boxes get smaller), and best way to describe it is
- "colorful static" pattern replaces the purple/black. After this hiccup,
- a moment of black, then taken to the gnome desktop. Things work fine.
- 
  If I close the lid, it seems that the computer flat-out doesn't wake up.
  HOWEVER, if I wait patiently more than 20 seconds, and press (not hold)
  the power button, SOMETIMES, the computer will "snap out of it" and come
  back to my desktop. Although RAM is 25% used, and CPU usage is around
  25-50% or less (depending on apps), mouse will regularly freeze up for
  some seconds every 10 seconds or so. Wifi will claim to be "on", but
  there aren't any networks in the "select network" dialogue. Turning wifi
  off and then on does not fix this problem. So I'll be in this terrifying
  state of non-responsive every few seconds computer, with no ability to
  reconnect to networks and report bug.
  
  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally", in that after
  I login, I get the "familiar" "colorful static" splash screen before
  being taken to normal functional gnome desktop experience.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  If I close the lid, it seems that the computer flat-out doesn't wake up.
  HOWEVER, if I wait patiently more than 20 seconds, and press (not hold)
  the power button, SOMETIMES, the computer will "snap out of it" and come
  back to my desktop. Although RAM is 25% used, and CPU usage is around
  25-50% or less (depending on apps), mouse will regularly freeze up for
  some seconds every 10 seconds or so. Wifi will claim to be "on", but
  there aren't any networks in the "select network" dialogue. Turning wifi
  off and then on does not fix this problem. So I'll be in this terrifying
  state of non-responsive every few seconds computer, with no ability to
  reconnect to networks and report bug.
  
  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
- restart again. Upon 2nd restart, it will boot "normally", in that after
- I login, I get the "familiar" "colorful static" splash screen before
- being taken to normal functional gnome desktop experience.
+ restart again. Upon 2nd restart, it will boot "normally".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about 

[Bug 1620688] Re: Evince crashed when a page of the pdf disapear

[Thom Wiggers]

** Also affects: evince (Arch Linux)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1620688

Title:
  Evince crashed when a page of the pdf disapear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1620688/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[tom]

Remove references to colorful static. The problem was these issues may or
may not be related, and both are not reportable in the usual way. I was
just mentioning all the serious symptoms of problems together, rather than
assuming they were all the result of a single discrete bug.

On Mar 8, 2018 21:51, "Daniel van Vugt" 
wrote:

> Tom, please try to report one issue per bug.
>
> We can either:
>
>  * make this a duplicate of bug 1753776 and you log a new bug for the
> other problem; or
>  * remove references to the first "static" problem from this bug.
>
> So please let us know how you'd like to proceed.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754425
>
> Title:
>   18.04 3.27 Gnome-shell Near-Fatalities
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   It's impossible to make a normal bug report, so here's the best I can
>   describe:
>
>   EVERY login to gnome, there is a moment after I enter my password and
>   press return, where whole screen goes small-resolution (cursor small,
>   all text and boxes get smaller), and best way to describe it is
>   "colorful static" pattern replaces the purple/black. After this
>   hiccup, a moment of black, then taken to the gnome desktop. Things
>   work fine.
>
>   If I close the lid, it seems that the computer flat-out doesn't wake
>   up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
>   hold) the power button, SOMETIMES, the computer will "snap out of it"
>   and come back to my desktop. Although RAM is 25% used, and CPU usage
>   is around 25-50% or less (depending on apps), mouse will regularly
>   freeze up for some seconds every 10 seconds or so. Wifi will claim to
>   be "on", but there aren't any networks in the "select network"
>   dialogue. Turning wifi off and then on does not fix this problem. So
>   I'll be in this terrifying state of non-responsive every few seconds
>   computer, with no ability to reconnect to networks and report bug.
>
>   I force restart. The first restart, upon login, will hang indefinitely
>   on a purple screen with the cursor in the middle. I will have to force
>   restart again. Upon 2nd restart, it will boot "normally", in that
>   after I login, I get the "familiar" "colorful static" splash screen
>   before being taken to normal functional gnome desktop experience.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.27.92-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
>   Uname: Linux 4.15.0-10-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Mar  8 12:38:24 2018
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2018-03-02 (5 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180228)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1754425/+subscriptions
>

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754218] Re: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected on a hybrid intel/nvidia system

[Daniel van Vugt]

** Summary changed:

- [regression] gdm 3.27 shows blank login screen on primary monitor when two 
monitors are connected
+ [regression] gdm 3.27 shows blank login screen on primary monitor when two 
monitors are connected on a hybrid intel/nvidia system

** Tags removed: multi-monitor
** Tags added: hybrid multimonitor

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1754218

Title:
  [regression] gdm 3.27 shows blank login screen on primary monitor when
  two monitors are connected on a hybrid intel/nvidia system

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1754218/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754564] [NEW] nautilus crash on double click on a file

[cubells]

Public bug reported:

On double click on a file like as test.txt, nautilus is closed suddenly
and file is not open.


$ G_DEBUG="all" NAUTILUS_DEBUG="All" nautilus
Gdk-Message: 06:47:01.176: Error 71 (Error de protocol) dispatching to Wayland 
display.


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
Codename:   bionic

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

** Package changed: evince (Ubuntu) => nautilus (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1754564

Title:
  nautilus crash on double click on a file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754564/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754218] Re: [regression] gdm 3.27 shows blank login screen on primary monitor when two monitors are connected

[Bug Watch Updater]

** Changed in: gdm
   Status: Unknown => Confirmed

** Changed in: gdm
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1754218

Title:
  [regression] gdm 3.27 shows blank login screen on primary monitor when
  two monitors are connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1754218/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754557] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Daniel van Vugt]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1748450, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1748450
   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 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754557/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754557] [NEW] gnome-shell crashed with signal 5 in g_log_default_handler()

[Karma Dorje]

Public bug reported:

this is an automated bug report.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Mar  9 02:43:53 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2015-08-05 (946 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754557/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753203] Bug 1753203

[Greg Trent]

Received an update on March 7 and now I can play an audio cd.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1753203

Title:
  unable to access audio disc in nautilus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1753203/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753203] Re: unable to access audio disc in nautilus

[Greg Trent]

Received an update on March 7 and now I can play audio CD's.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1753203

Title:
  unable to access audio disc in nautilus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1753203/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754401] Re: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

[Daniel van Vugt]

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1754401

Title:
  Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console
  1 (Permission denied)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754401/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[Daniel van Vugt]

Tom, please try to report one issue per bug.

We can either:

 * make this a duplicate of bug 1753776 and you log a new bug for the other 
problem; or
 * remove references to the first "static" problem from this bug.

So please let us know how you'd like to proceed.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754401] Re: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

[Daniel van Vugt]

** Summary changed:

- gdm-x-session xf86OpenConsole: Cannot open virtual console 1 (Permission 
denied)
+ Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 
(Permission denied)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1754401

Title:
  Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console
  1 (Permission denied)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754401/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753078] Re: gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() from file_to_buffer()

[Daniel van Vugt]

Thanks. I think I've found the related packages now. See above.

** Also affects: libgtop2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libgtop2 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** Also affects: gnome-shell-extension-system-monitor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-system-monitor (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler()
  from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from
  glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753078/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754077] Re: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed

[Daniel van Vugt]

Thanks. I can't seem to find any other reports of this crash yet,
although that's also partly due to errors.ubuntu.com not responding
today...

Please help us to gather a .crash file next time this problem occurs by:
1. Apply the workaround from bug 994921 now.
2. Next time the crash occurs, look in /var/crash for new files and then run:
   ubuntu-bug /var/crash/YOURFILE.crash
3. Let us know here the ID of the new bug the above command created.

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  (gnome-shell:26479): GLib-GObject-CRITICAL **:
  g_signal_handler_disconnect: assertion 'handler_id > 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754445] Re: gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_icon_theme_changed()

[Daniel van Vugt]

Dropped importance to Low, because the stack trace suggests this crash
could only happen when changing the icon theme(?)

** Summary changed:

- gnome-shell crashed with SIGSEGV in cogl_object_unref()
+ gnome-shell crashed with SIGSEGV in cogl_object_unref() from 
iter_remove_or_steal() from g_hash_table_iter_remove() from 
st_texture_cache_evict_icons() from on_icon_theme_changed()

** Information type changed from Private to Public

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => Low

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_object_unref() from
  iter_remove_or_steal() from g_hash_table_iter_remove() from
  st_texture_cache_evict_icons() from on_icon_theme_changed()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754445/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754477] Re: totem crashed with SIGSEGV in memcpy() from gen8_render_init() from i965_Init() from __vaDriverInit_1_0()

[Daniel van Vugt]

** Summary changed:

- totem crashed with SIGSEGV in memcpy()
+ totem crashed with SIGSEGV in memcpy() from gen8_render_init() from 
i965_Init() from __vaDriverInit_1_0()

** Information type changed from Private to Public

** Also affects: intel-vaapi-driver (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: intel-vaapi-driver (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1754477

Title:
  totem crashed with SIGSEGV in memcpy() from gen8_render_init() from
  i965_Init() from __vaDriverInit_1_0()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1754477/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754491] Re: "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

[Daniel van Vugt]

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1754491

Title:
  "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754491/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1720685] Re: nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name()

[Matt Zilmer]

Similar to earlier-reported.  The server went down while this client was
using it, which may be a different circumstance.

z

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1720685

Title:
  nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720685/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754520] Re: gnome-control-center crashed while changing dock icons size

[Apport retracing service]

*** This bug is a duplicate of bug 1723249 ***
https://bugs.launchpad.net/bugs/1723249

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1723249, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1754520/+attachment/5073815/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1754520/+attachment/5073817/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1754520/+attachment/5073820/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1754520/+attachment/5073821/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1754520/+attachment/5073822/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754520/+attachment/5073823/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754520/+attachment/5073824/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1723249
   gnome-control-center crashed with SIGSEGV in maybe_add_app_id()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed while changing dock icons size

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754520/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754491] [NEW] "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

[AsciiWolf]

Public bug reported:

It looks like that the "Ubuntu on Wayland" translation disappeared after
some recent Ubuntu 18.04 update, although the string is fully translated
on Launchpad.

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

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic l10n

** Also affects: gdm3 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754491/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Scott Moser]

** No longer affects: maas

** No longer affects: nplan (Ubuntu)

** No longer affects: systemd (Ubuntu)

** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => Medium

** Changed in: cloud-init
 Assignee: (unassigned) => Ryan Harper (raharper)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1750884

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754491] [NEW] "Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug by AsciiWolf (asciiwolf):

It looks like that the "Ubuntu on Wayland" translation disappeared after
some recent Ubuntu 18.04 update, although the string is fully translated
on Launchpad.

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic l10n
-- 
"Ubuntu on Wayland" string not translated anymore on Ubuntu 18.04
https://bugs.launchpad.net/bugs/1754491
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to the bug report.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1752299] Re: [RFE] Show snaps in "Recent Releases"

[AsciiWolf]

Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-
software/issues/314

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

Title:
  [RFE] Show snaps in "Recent Releases"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1752299/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754156] Re: Screen unlocking without password

[pumpkinbeer]

** Information type changed from Private Security to Public Security

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

Title:
  Screen unlocking without password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1754156/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

[amano]

It just happens in the Ubuntu-Wayland session. It doesn't happen in the
default Ubuntu session. Added the wayland tag.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1754169

Title:
  [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754472] [NEW] autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there

[ChristianEhrhardt]

Public bug reported:

The test really seems to be triggered all of the time to resolve a flaky test.
That is just not worth the test.
But it provides goo coverage, so an override in britney would loose all that.

Lets skip the offending test on the arch it is known to be flaky
(s390x).

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754472

Title:
  autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754437] Re: gnome-shell crashed with signal 5

[Apport retracing service]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073342/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073344/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073347/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073348/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073349/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073350/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754437/+attachment/5073351/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   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 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754437/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754436] Re: evolution-addressbook-factory-subprocess crashed with SIGABRT in std::terminate()

[Apport retracing service]

*** This bug is a duplicate of bug 1724277 ***
https://bugs.launchpad.net/bugs/1724277

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1724277, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1754436/+attachment/5073332/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1754436/+attachment/5073334/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1754436/+attachment/5073337/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1754436/+attachment/5073338/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1754436/+attachment/5073339/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754436/+attachment/5073340/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754436/+attachment/5073341/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1724277

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1754436

Title:
  evolution-addressbook-factory-subprocess crashed with SIGABRT in
  std::terminate()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1754436/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[tom]

** This bug is no longer a duplicate of bug 1753776
   Graphics corruption in login animation to Xorg sessions

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[tom]

*** This bug is a duplicate of bug 1753776 ***
https://bugs.launchpad.net/bugs/1753776

Thanks Jeremy. That bug definitely describes the normal login behavior I
see. However, the main part of this bug is strange behavior after
closing the lid, and the failed first restart freezing on purple screen.

So, while part of this bug report is duplicate, part of it is not (so
far as I know).

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753776] Re: Graphics corruption in login animation to Xorg sessions

[Jeremy Bicha]

** Tags added: rls-bb-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1753776

Title:
  Graphics corruption in login animation to Xorg sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753776/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[Jeremy Bicha]

*** This bug is a duplicate of bug 1753776 ***
https://bugs.launchpad.net/bugs/1753776

Thank you for taking the time to report this bug. This bug has already
been reported as #1753776 so I am marking it a duplicate.

** This bug has been marked a duplicate of bug 1753776
   Graphics corruption in login animation to Xorg sessions

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754425] Re: 18.04 3.27 Gnome-shell Near-Fatalities

[tom]

The colorful static looks like this, but colorful:
https://i.stack.imgur.com/GQQxy.jpg

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754425] [NEW] 18.04 3.27 Gnome-shell Near-Fatalities

[tom]

Public bug reported:

It's impossible to make a normal bug report, so here's the best I can
describe:

EVERY login to gnome, there is a moment after I enter my password and
press return, where whole screen goes small-resolution (cursor small,
all text and boxes get smaller), and best way to describe it is
"colorful static" pattern replaces the purple/black. After this hiccup,
a moment of black, then taken to the gnome desktop. Things work fine.

If I close the lid, it seems that the computer flat-out doesn't wake up.
HOWEVER, if I wait patiently more than 20 seconds, and press (not hold)
the power button, SOMETIMES, the computer will "snap out of it" and come
back to my desktop. Although RAM is 25% used, and CPU usage is around
25-50% or less (depending on apps), mouse will regularly freeze up for
some seconds every 10 seconds or so. Wifi will claim to be "on", but
there aren't any networks in the "select network" dialogue. Turning wifi
off and then on does not fix this problem. So I'll be in this terrifying
state of non-responsive every few seconds computer, with no ability to
reconnect to networks and report bug.

I force restart. The first restart, upon login, will hang indefinitely
on a purple screen with the cursor in the middle. I will have to force
restart again. Upon 2nd restart, it will boot "normally", in that after
I login, I get the "familiar" "colorful static" splash screen before
being taken to normal functional gnome desktop experience.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  8 12:38:24 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-03-02 (5 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  18.04 3.27 Gnome-shell Near-Fatalities

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754425/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 716280] Re: gvfsd-metadata process pegs CPU while nautilus waits

[Daniel Llewellyn]

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/716280

Title:
  gvfsd-metadata process pegs CPU while nautilus waits

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/716280/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 826283] Re: size of internal HDDs differs/wrong

[Daniel Llewellyn]

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

I've marked "Ubuntu Translations" as invalid because I do not believe it
is related to the text translations.

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: ubuntu-translations
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/826283

Title:
  size of internal HDDs differs/wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/826283/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 823168] Re: gvfs webdav to common name

[Daniel Llewellyn]

This is a really old bug and things may be different now. Can you verify
whether this is still a problem on Xenial (16.04) or Artful (17.10) and
reset the bug to "confirmed" if you can recreate the issue?

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/823168

Title:
  gvfs webdav to common name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/823168/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 874471] Re: Pendrive/USB drive cannot be open in folder

[Daniel Llewellyn]

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/874471

Title:
  Pendrive/USB drive cannot be open in folder

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/874471/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 312722] Re: Connect to FTP with Login > Error "The file is not a directory"

[Daniel Llewellyn]

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/312722

Title:
  Connect to FTP with Login > Error "The file is not a directory"

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/312722/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 708546] Re: USB keys freeze the computer

[Daniel Llewellyn]

This is a really old bug and the versions of Ubuntu it references are
out of support now. Can you verify whether this is still a problem on
Xenial (16.04) or Artful (17.10) and reset the bug to "confirmed" if you
can recreate the issue.

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/708546

Title:
  USB keys freeze the computer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/708546/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754403] Re: gnome-shell crashed with signal 5

[Apport retracing service]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073200/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073202/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073205/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073206/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073207/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073208/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754403/+attachment/5073209/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   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 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754403/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754401] Re: gdm-x-session xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

[Simon Déziel]

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754401/+attachment/5073196/+files/Xorg.0.log

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1754401

Title:
  gdm-x-session xf86OpenConsole: Cannot open virtual console 1
  (Permission denied)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754401/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754401] [NEW] gdm-x-session xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

[Simon Déziel]

Public bug reported:

I don't what changed but today, my Artful laptop refuses to start a
graphical session. The last update seems entirely unrelated:

# /var/log/apt/history.log
Start-Date: 2018-03-06  15:50:35
Commandline: apt-get dist-upgrade
Requested-By: simon (1000)
Upgrade: libpq5:amd64 (9.6.7-0ubuntu0.17.10, 9.6.8-0ubuntu0.17.10)
End-Date: 2018-03-06  15:50:39

I tried linux-image-4.13.0-32-generic and linux-image-4.13.0-36-generic
to no avail. I removed the "quiet splash" args from /etc/default/grub
but it didn't help. Using "nomodeset" makes the graphical session almost
work but the brightness of the screen is so low that I cannot use it and
can't make it brighter either.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.1-3ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Thu Mar  8 11:08:35 2018
InstallationDate: Installed on 2017-10-21 (137 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1754401

Title:
  gdm-x-session xf86OpenConsole: Cannot open virtual console 1
  (Permission denied)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1754401/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1164016] Re: restore type-ahead find

[teo1978]

> If that is genuinely the reason (and this bug has been marked as "Fix 
> Released" 
> since Jan 2014, so it seems correct), then is it not time to raise a new bug?

Maybe (though it seems a little stupid to raise a new bug for exactly
the same issue).

Anyway I did, like yesterday, and it got closed
(can't find it right now, I don't know what's wrong with the search engine of 
this stupid bug tracker)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1164016

Title:
  restore type-ahead find

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)

[teo1978]

This is so stupid.

> One of my main interests in the last 4 releases was to improve this 
> situation, whether search doesn't replace the use cases of type ahead.

Indeed, search, does NOT replace type-ahead, it's just a completely
different thing, and it won't ever be a replacement, no matter how much
you improve it, and regardless of performance.

The solution was pretty obvious: just DON'T replace type-ahead with
search.

But no, idiocy had to prevail, as it usually does in Nautilus. That's a
shame.

I wonder why Ubuntu doesn't switch to some other file manager that,
unlike Nautilus, is not maintained by complete idiots.

I guess I'll have to switch to a distro that, unlike Ubuntu, is not
maintained by idiots either.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/181

Title:
  Restore interactive_search.patch (type-ahead search)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

[Ubuntu Foundations Team Bug Bot]

The attachment "xenial SRU debdiff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu.
https://bugs.launchpad.net/bugs/1754356

Title:
  xdg-user-dirs-update does not take care of $HOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1708409] Re: kdump service does not start after configure/reboot

[Andrew Cloke]

** Changed in: makedumpfile (Ubuntu Artful)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1708409

Title:
  kdump service does not start after configure/reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1754125] Re: Rhythmbox stays running in the background after quit

[James Benton Jr]

I have tried CTRL+Q. Still does not shut down. The only way is to kill the
process.

On Wed, Mar 7, 2018 at 5:30 PM, Gustavo Silva <1754...@bugs.launchpad.net>
wrote:

> How are you closing RhythmBox? The program is not actually closed if
> music is playing and you press the X on the top right corner. Usually I
> had to do CTRL+Q if I wanted to actually shut it down. Can you try this?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1754125
>
> Title:
>   Rhythmbox stays running in the background after quit
>
> Status in rhythmbox package in Ubuntu:
>   New
>
> Bug description:
>   If you do ps -alx you will see rhythmbox process still running. It
>   causes opening rhythmbox to hang when trying to open again
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: rhythmbox 3.4.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
>   Uname: Linux 4.15.0-10-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Mar  7 13:21:51 2018
>   InstallationDate: Installed on 2018-03-07 (0 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180307)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: rhythmbox
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   XorgLog: Error: [Errno 2] No such file or directory:
> '/var/log/Xorg.0.log'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/
> 1754125/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1754125

Title:
  Rhythmbox stays running in the background after quit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Andres Rodriguez]

** Changed in: maas
   Importance: High => Medium

** Changed in: maas
   Status: Won't Fix => Triaged

** Changed in: maas
   Importance: Medium => Low

** Changed in: maas
Milestone: None => 2.4.x

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1750884

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Mike Pontillo]

** Changed in: maas
   Status: Triaged => Won't Fix

** Changed in: maas
 Assignee: Mike Pontillo (mpontillo) => (unassigned)

** Changed in: maas
Milestone: 2.4.0alpha2 => None

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1750884

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753776] Re: Graphics corruption in login animation to Xorg sessions

[Andrea Azzarone]

I still get this when starting a X session.

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.27.92-0ubuntu1
  Candidate: 3.27.92-0ubuntu1
  Version table:
 *** 3.27.92-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1753776

Title:
  Graphics corruption in login animation to Xorg sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753776/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753203] Re: unable to access audio disc in nautilus

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1753203

Title:
  unable to access audio disc in nautilus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1753203/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

[Sebastien Bacher]

whatever gedit is doing nautilus shouldn't hit a segfault, not a gedit
bug

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1754169

Title:
  [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: gedit (Ubuntu)
   Importance: Undecided => High

** Changed in: gedit (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1754169

Title:
  [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

[Treviño]

** Patch added: "bionic fix"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+attachment/5073085/+files/xdg-user-dirs-update-give-priority-to-HOME-bionic.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu.
https://bugs.launchpad.net/bugs/1754356

Title:
  xdg-user-dirs-update does not take care of $HOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

[Treviño]

** Patch added: "xenial SRU debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+attachment/5073084/+files/xdg-user-dirs-update-give-priority-to-HOME.debdiff

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu.
https://bugs.launchpad.net/bugs/1754356

Title:
  xdg-user-dirs-update does not take care of $HOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754356] [NEW] xdg-user-dirs-update does not take care of $HOME

[Treviño]

Public bug reported:

[ Impact ]

When setting an user dir to a folder that is subfolder of $HOME (and
when $HOME does not match the /etc/passwd defined home for the user),
the ~/.config/user-dirs.dirs is wrongly generated.

[ Test case ]

 1) env HOME=/tmp/temp-home xdg-user-dirs-update
 2) find /tmp/temp-home/
 3) should list generated XDG user directories
 4) /tmp/temp-home/.config/user-dirs.dirs should mention them

Launching something like:
 - env HOME=/tmp/temp-home ./xdg-user-dirs-update --set DOWNLOADS 
"/tmp/temp-home/sub/folder/of/it/Downloads"

Should modify /tmp/temp-home/.config/user-dirs.dirs so that it contains:
  XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"

[ Regression potential ]

Xdg folders could be generated in wrong locations.

** Affects: xdg-user-dirs (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress


** Tags: patch

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu.
https://bugs.launchpad.net/bugs/1754356

Title:
  xdg-user-dirs-update does not take care of $HOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: snapd-glib (Ubuntu Artful)
   Status: New => Confirmed

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-software (Ubuntu Artful)
   Status: New => Confirmed

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: snapd-glib (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  gnome-software spams error messages to journald and causes 100% CPU
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1723362/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754169] Re: [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

[Jeremy Bicha]

I cannot duplicate this bug with the X session, only with Wayland.

** Summary changed:

- [Bionic] Nautilus crashes when a file is opened with gedit
+ [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

** Description changed:

  See title.
  
  ==Steps to reproduce==
+ 0) From the log in screen, click your name, then click the gear button and 
select Ubuntu on Wayland. Log in.
  1) Open nautilus (currently 3.26.2 in bionic)
  2) Browse to a location with a textfile (eg. /home/user/.thunderbird )
  3) Right click a textfile (eg. profiles.ini)
  4) Choose gedit from the list (probably default), click ok.
  5) Nautilus crashes, gedit doesn't come up
  
  ==Expected result==
  Nautilus doesn't crash, gedit comes up and lets you edit the file
  
  ==Why (probably) a gedit regression==
  When choosing LibreOffice Nautilus doesn't crash and LibreOffice opens the 
file.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Mar  7 22:13:00 2018
  InstallationDate: Installed on 2018-02-23 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: wayland

** Tags added: rls-bb-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1754169

Title:
  [Bionic] [wayland] Nautilus crashes when a file is opened with gedit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1754169/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754332] [NEW] /var/log/journal not created on fresh install of systemd

[Dan Watkins]

Public bug reported:

(Such as during image builds.)

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
 Status: New


** Tags: amd64 apport-bug bionic

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Description changed:

  (Such as during image builds.)
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: systemd 237-3ubuntu4
- ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
- Uname: Linux 4.15.0-10-generic x86_64
- ApportVersion: 2.20.8-0ubuntu10
- Architecture: amd64
- CurrentDesktop: ubuntu:GNOME
- Date: Thu Mar  8 14:38:21 2018
- InstallationDate: Installed on 2017-10-23 (135 days ago)
- InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
- MachineType: LENOVO 20ANCTO1WW
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
- SourcePackage: systemd
- SystemdDelta:
-  [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
-  [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
-  
-  2 overridden configuration files found.
- UpgradeStatus: Upgraded to bionic on 2018-01-23 (44 days ago)
- dmi.bios.date: 05/21/2014
- dmi.bios.vendor: LENOVO
- dmi.bios.version: GLET70WW (2.24 )
- dmi.board.asset.tag: Not Available
- dmi.board.name: 20ANCTO1WW
- dmi.board.vendor: LENOVO
- dmi.board.version: SDK0E50512 STD
- dmi.chassis.asset.tag: No Asset Information
- dmi.chassis.type: 10
- dmi.chassis.vendor: LENOVO
- dmi.chassis.version: Not Available
- dmi.modalias: 
dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
- dmi.product.family: ThinkPad T440p
- dmi.product.name: 20ANCTO1WW
- dmi.product.version: ThinkPad T440p
- dmi.sys.vendor: LENOVO

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754332

Title:
  /var/log/journal not created on fresh install of systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754332/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown

[Rick]

Same issue in Mint 18.3 Cinnamon with all updates

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

Title:
  GNOME Keyring Daemon stops panel's shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754310] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1754310/+attachment/5072823/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1754310/+attachment/5072825/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1754310/+attachment/5072828/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1754310/+attachment/5072829/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1754310/+attachment/5072830/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754310/+attachment/5072831/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1754310/+attachment/5072832/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1748450
   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 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754310/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754077] ProcEnviron.txt

[isma]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1754077/+attachment/5072800/+files/ProcEnviron.txt

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

Title:
  (gnome-shell:26479): GLib-GObject-CRITICAL **:
  g_signal_handler_disconnect: assertion 'handler_id > 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754077] JournalErrors.txt

[isma]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1754077/+attachment/5072798/+files/JournalErrors.txt

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

Title:
  (gnome-shell:26479): GLib-GObject-CRITICAL **:
  g_signal_handler_disconnect: assertion 'handler_id > 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754077] ProcCpuinfoMinimal.txt

[isma]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1754077/+attachment/5072799/+files/ProcCpuinfoMinimal.txt

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

Title:
  (gnome-shell:26479): GLib-GObject-CRITICAL **:
  g_signal_handler_disconnect: assertion 'handler_id > 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754077] Re: (gnome-shell:26479): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion 'handler_id > 0' failed

[isma]

apport information

** Tags added: apport-collected third-party-packages xenial

** Description changed:

- Some times gnomeshell just gets stuck and crashes. I keep sending the
- bug reports automatically with the tool, and updating the system, but
- the issue is still there.
+ Some times gnomeshell just gets stuck and crashes. I keep sending the bug 
reports automatically with the tool, and updating the system, but the issue is 
still there.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 16.04
+ GsettingsChanges:
+  org.gnome.shell enabled-extensions ['nohotcor...@azuri.free.fr', 
'topic...@phocean.net']
+  org.gnome.shell command-history ['gconf-editor', 'dconf-editor', 'r', 
'xrandr', 'r', 'right_mouse.sh', 'r', 'R', 'r', 'terminal', 'term', 'r', 
'gnome-desktop-item-edit --create-new ~/Desktop', 'r']
+  org.gnome.shell favorite-apps ['firefox.desktop', 'evolution.desktop', 
'libreoffice-writer.desktop', 'org.gnome.Nautilus.desktop', 
'chromium-browser.desktop', 'yelp.desktop', 'Mattermost.desktop', 
'skypeforlinux.desktop', 'google-chrome.desktop']
+  org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple'
+ InstallationDate: Installed on 2017-06-14 (267 days ago)
+ InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
+ Package: gnome-shell 3.18.5-0ubuntu0.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
+ Tags: third-party-packages xenial
+ Uname: Linux 4.13.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1754077/+attachment/5072797/+files/Dependencies.txt

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

Title:
  (gnome-shell:26479): GLib-GObject-CRITICAL **:
  g_signal_handler_disconnect: assertion 'handler_id > 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754077/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1750289] Re: gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()

[Trent Lloyd]

This happens for me also but with FAT, reformatting an existing
partition

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

Title:
  gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1750289/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753078] Re: gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() from file_to_buffer()

[shemgp]

I think the extension that's monitoring the CPU, which I'm using, is
this: https://extensions.gnome.org/extension/120/system-monitor/

None extension.gnome.org extension that I'm using is
https://github.com/lestcape/Gnome-Global-AppMenu

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

Title:
  gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler()
  from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from
  glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753078/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754283] Re: Totem is stuttering in Xorg sessions (but not in Wayland sessions)

[Daniel van Vugt]

*** This bug is a duplicate of bug 1698270 ***
https://bugs.launchpad.net/bugs/1698270

** This bug has been marked a duplicate of bug 1698270
   Totem pauses and stutters during video playback even when CPU usage is low

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1754283

Title:
  Totem is stuttering in Xorg sessions (but not in Wayland sessions)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1754283/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754284] [NEW] Totem is tearing when fullscreen in Xorg sessions

[Daniel van Vugt]

Public bug reported:

Totem is tearing when fullscreen in Xorg sessions.

This is probably to do with composite unredirecting... In compiz we have
a workaround to avoid this tearing by disallowing unredirect ("bypass")
in known problematic video players. But I'm not sure if mutter has such
a workaround/whitelist/blacklist we can use.

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

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


** Tags: bionic visual-quality

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: bionic visual-quality

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1754284

Title:
  Totem is tearing when fullscreen in Xorg sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1754284/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754283] [NEW] Totem is stuttering in Xorg sessions (but not in Wayland sessions)

[Daniel van Vugt]

*** This bug is a duplicate of bug 1698270 ***
https://bugs.launchpad.net/bugs/1698270

Public bug reported:

Totem is stuttering in Xorg sessions (but not in Wayland sessions).

This doesn't seem to be related to VAAPI either, as removing that shows
the same problem was software decoding. There's something wrong with the
X11/Xorg rendering in totem.

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


** Tags: bionic performance visual-quality

** Tags added: bionic performance

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: mutter (Ubuntu)

** Tags added: visual-quality

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1754283

Title:
  Totem is stuttering in Xorg sessions (but not in Wayland sessions)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1754283/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1754270] [NEW] systemd-user PAM configuration should initialize the keyring with pam_keyinit

[Trent Lloyd]

Public bug reported:

/etc/pam.d/systemd-user does not currently call pam_keyinit.so -- it's
possible this should instead be added to common-session-noninteractive
but I am not entirely sure about that - someone with more understanding
of the PAM modules would probably need to weigh in on that.  In any case
systemd-user itself should at least have it - as it has it's own special
PAMname for processes it launches.

This means that the keyring does not link to the user keyring as it
should, and will cause issues with programs needing a key from the
keyring.  In particular the use case that breaks for me is using
'fscrypt' and 'libpam-fscrypt' however anything making use of kernel
keyrings would be affected.

Something non-obvious about this, is that many desktop session processes
are started under 'systemd-user' instead of the 'session' - this
includes gnome-terminal-server which means any gnome-terminal shell runs
under this context.  If you start xterm instead of gnome-terminal, you
get a different keyring and this can cause confusion when debugging the
issue as some processes are in one state and the others are in another
including your primary debug tool gnome-terminal.  You can verify this
by running 'systemctl status $(pidof gnome-terminal)' and 'systemctl
status $(pidof xterm)' and note the different hierachy.

The change to add pam_keyinit.so was made upstream in December 2016:
https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f

Ubuntu should make the same change so that services needing a keyring
will work correctly in the desktop session, and the same keyring is used
for processes launched under both methods.  In my test I add the usual
pam_keyinit.so line after "pam_limits.so" and before "common-session-
noninteractive".  I am not sure if this is the most ideal location (but
it appears to work).


You can test the behavior by running "keyctl show @s" in both contexts

Working contexts:
- xterm
- SSH login

Broken contexts:
- gnome-terminal
- systemd-run --user keyctl show @s (then check output with journalctl --user 
--follow)


When the configuration is broken you will see this output:
lathiat@ubuntu:~/src/systemd$ keyctl show @s
Keyring
  59654779 --alswrv   1000  1000  keyring: _ses
   6806191 s-rv  0 0   \_ user: invocation_id

When the configuration is working, you will see a link to the user session 
instead:
lathiat@ubuntu:~/src/systemd$ keyctl show @s
Keyring
  59654779 --alswrv   1000  1000  keyring: _ses
   6806191 s-rv  0 0   \_ keyring: _uid.1000


As background, what is broken on my test setup with libpam-fscrypt?
gnome-terminal for example is unable to write any file in my encrypted /home 
which means that it cannot save preferences, so if you go into preferences and 
try to tick a checkbox it will immediately revert and an error is logged to the 
journal.  You can use the guide at https://github.com/google/fscrypt to setup 
such a system if you wish to fully test my case.  But you can simply verify the 
behavior as above.

Verified on bionic (its the only version with fscrypt) however this
issue extends back to at least xenial.

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1754270

Title:
  systemd-user PAM configuration should initialize the keyring with
  pam_keyinit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754270/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs