[Bug 1792668] Re: gnome-calendar fails to sync, update, or cache

2018-09-16 Thread ethanay
I am renaming all "evolution" folders in ~.config ~.cache and
~.local/share to see if that fixes the behavior.

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

Title:
  gnome-calendar fails to sync, update, or cache

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

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

[Bug 1792668] Re: gnome-calendar fails to sync, update, or cache

2018-09-16 Thread ethanay
Experiencing similar issues/behavior in other gnome office apps:
contacts and todo list.

Contacts has actually given a useful error when trying to edit a google
contact, but the error message disappears very quickly and cannot be
copied or pasted. Attached is a screenshot.

This is all occurring on a fresh install. All I did was install the
software, link my google accounts, and try to run the apps. For some
reason, they are not self-configuring with the google accounts
correctly.

?field.comment=Experiencing similar issues in other gnome office apps:
contacts and todo list.

Contacts has actually given a useful error, but the error message
disappears very quickly and cannot be copied or pasted. Attached is a
screenshot.

This is all occurring on a fresh install. All I did was install the
software, link my google accounts, and try to run the apps. For some
reason, they are not self-configuring with the google accounts
correctly.


** Attachment added: "Screenshot of error message related to issues experienced"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1792668/+attachment/5189716/+files/Screenshot%20from%202018-09-17%2014-17-00.png

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

Title:
  gnome-calendar fails to sync, update, or cache

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

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

[Bug 1626347] Re: Blank screen after logging in with GDM

2018-09-16 Thread Launchpad Bug Tracker
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Blank screen after logging in with GDM

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

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

[Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?

2018-09-16 Thread Graham Wheeler
** Description changed:

- So yesterday I got the prompt to upgrade my 16LTS system to 18. Man am I
- sorry I went ahead with this; I am in a world of hurt. But the most
- frustrating issue out of many has to be this one.
+ So yesterday I got the prompt to upgrade my 16LTS system to 18. This
+ caused a number of issues, but the most frustrating issue out of many
+ has to be this one.
  
  After a period of inactivity, the lock screen kicks in. When I then try
  to log in, using the correct password, I get a spinner for about 10
  seconds, the "Authentication error".
  
  After a couple of seconds "Authentication error" goes away but now it
  seems no keys are registering at all in the password field. I say "it
  seems" because I see no "*"s as I type, but I do see occasional prompts
  of "Authentication error" coming back, but I haven't pinpointed the
  circumstances - certainly not triggered by hitting ENTER, sometimes
  backspace? Not sure if it has anything to do with the keys.
  
  After this all I can do is log in over ssh and reboot; I'm basically
  locked out on the console.
  
+ If I wait a while the keyboard does seem to come back but the problem is
+ still there - my password is not accepted and then the keyboard again
+ seems to do nothing for a while.
+ 
  This happens whether I have a USB keyboard connected or whether I am
  running Synergy and using a virtual keyboard. Mouse continues to work
  fine.
  
  Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic
  x86_64)

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

Title:
  GDM lock screen will not accept credentials and then loses keyboard?

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

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

[Bug 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?

2018-09-16 Thread Graham Wheeler
A bit more about this - if I wait a while the keyboard does seem to come
back but the problem is still there - my password is not accepted and
then the keyboard does nothing for a while.

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

Title:
  GDM lock screen will not accept credentials and then loses keyboard?

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

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

[Bug 1792843] [NEW] GDM lock screen will not accept credentials and then loses keyboard?

2018-09-16 Thread Graham Wheeler
Public bug reported:

So yesterday I got the prompt to upgrade my 16LTS system to 18. Man am I
sorry I went ahead with this; I am in a world of hurt. But the most
frustrating issue out of many has to be this one.

After a period of inactivity, the lock screen kicks in. When I then try
to log in, using the correct password, I get a spinner for about 10
seconds, the "Authentication error".

After a couple of seconds "Authentication error" goes away but now it
seems no keys are registering at all in the password field. I say "it
seems" because I see no "*"s as I type, but I do see occasional prompts
of "Authentication error" coming back, but I haven't pinpointed the
circumstances - certainly not triggered by hitting ENTER, sometimes
backspace? Not sure if it has anything to do with the keys.

After this all I can do is log in over ssh and reboot; I'm basically
locked out on the console.

This happens whether I have a USB keyboard connected or whether I am
running Synergy and using a virtual keyboard. Mouse continues to work
fine.

Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic
x86_64)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: 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/1792843

Title:
  GDM lock screen will not accept credentials and then loses keyboard?

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

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

[Bug 1731524] Re: mate panel freezes when clicking on fcitx icon in the notification area while having a text field selected

2018-09-16 Thread Walter Lapchynski
** Also affects: fcitx (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mate panel freezes when clicking on fcitx icon in the notification
  area while having a text field selected

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

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

[Bug 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output

2018-09-16 Thread Sapa Holliday
Forgiven, I am also sorry if I have wasted anyone's time.

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

Title:
  Pango-WARNING **: shaping failure, expect ugly output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+subscriptions

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

[Bug 874983] Re: Epiphany 3 always automatically download files

2018-09-16 Thread Jeremy Bicha
Yes, GNOME GitLab isn't support by Launchpad's bug tracker yet. LP:
#1738870

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

Title:
  Epiphany 3 always automatically download files

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/874983/+subscriptions

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

[Bug 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output

2018-09-16 Thread Tong Sun
Sorry, I apologize. One thing I didn't mention is that this issue was
already nearly 2 years old, and has a clear cause, so it is very
unlikely to relate to any other recent issues. But anyway. Sorry for my
bad attitude.

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

Title:
  Pango-WARNING **: shaping failure, expect ugly output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+subscriptions

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

[Bug 1792403] Re: Nautilus 3.30 in Gnome Staging PP does not start without tracker package

2018-09-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Nautilus 3.30 in Gnome Staging PP does not start without tracker
  package

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

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

[Bug 874983] Re: Epiphany 3 always automatically download files

2018-09-16 Thread Goyo
This bug has been obsoleted in GNOME bugzilla because it has been migrated to 
GitLab.
https://gitlab.gnome.org/GNOME/epiphany/issues/147

Apparently I can neither change the status nor the remote bug watch.

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

Title:
  Epiphany 3 always automatically download files

To manage notifications about this bug go to:
https://bugs.launchpad.net/epiphany-browser/+bug/874983/+subscriptions

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

[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console

2018-09-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gdm3 (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  Login password from GDM is shown in plain text on the VT1 console

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

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

[Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed

2018-09-16 Thread Jeremy Bicha
It looks like both Brad and Helen were using the workspace-grid
extension so that may be the broken extension here.

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

Title:
  [Cosmic] gnome-shell crashes when windows key pressed

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

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

[Bug 1639513] Re: Pango-WARNING **: shaping failure, expect ugly output

2018-09-16 Thread Sapa Holliday
Tong Sun Please don't be unfriendly.

I saw a similarity in that you have the same two files that conflict in
my own example.

I thought if they conflict for me then they may conflict for you.

They are
 
libpango1.0-0:amd64_1.38.1-1
libpango-1.0-0:amd64_1.38.1-1

they are from two different releases

I thought that people having problems with the same files would want to
share ideas

I won't comment here again as you don't want me to.

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

Title:
  Pango-WARNING **: shaping failure, expect ugly output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1639513/+subscriptions

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

[Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed

2018-09-16 Thread Helen M. Koike Fornazier
I saw through https://extensions.gnome.org/local/ that there was some
extensions in "ERROR" state.

I removed those and it works now (at least in Debian Sid), I hope this
helps.

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

Title:
  [Cosmic] gnome-shell crashes when windows key pressed

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

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

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
Oh, I see. It does not work anyway in 18.04

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

Title:
  gnome-screensaver-command --lock starts the daemon

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

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

[Bug 1788691] Re: [Cosmic] gnome-shell crashes when windows key pressed

2018-09-16 Thread Helen M. Koike Fornazier
Seems related, I have this same issue in Debian sid:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908769

It happen consistently to me when the machines returns from suspend, I
login and I press the super key.

Brad, could you check if this always happens just after suspend? Just to
check if we have the same issue.

** Bug watch added: Debian Bug tracker #908769
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908769

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

Title:
  [Cosmic] gnome-shell crashes when windows key pressed

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

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

[Bug 1777848] Re: screen never locks

2018-09-16 Thread Theo Linkspfeifer
Running gnome-screensaver in debug mode led me to bug 864458.

I have only tested it in a live session, so it may not be disabled in a
normal session.

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

Title:
  screen never locks

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

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

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Theo Linkspfeifer
Tested in 18.04, and the command did spawn gnome-screensaver --no-
daemon.

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

Title:
  gnome-screensaver-command --lock starts the daemon

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

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

[Bug 1731985] Re: Nautilus now makes random beeps on some navigation actions, and I can't turn it off

2018-09-16 Thread teo1978
Mistery solved:

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792722/comments/2

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => 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/1731985

Title:
  Nautilus now makes random beeps on some navigation actions, and I
  can't turn it off

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

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

[Bug 1792722] Re: Ubuntu patches to nautilus get randomly reverted again and again

2018-09-16 Thread teo1978
I found out what triggers this issue!

This happens when I restart (by killing it) unity-settings-daemon as a
workaround to infamous bug 1731294.

And now I see that there is a workaround to the workaround.

After killing unity-settings-daemon (which restarts automatically),
which leaves Nautilus all screwed up with its crappy font, its stupid
random beep sounds, and its unusable mess of menus, I have to kill every
last running instance of Nautilus (it's not enough to close all nautilus
window, you need to kill the one responsible for the Desktop), and
restart it. Then it works as expected.


Note that, even though this surfaces as a consequence of a workaround to issue 
1731294, this is an issue on its own: restarting unity-settings-daemon 
shouldn't leave a running instance of Nautilus in a crippled state. Either 
Nautilus should restart automatically if necessary, or it shouldn't be affected 
in the first place.

I don't know whether this is unity-settings-daemon's fault or Nautilus'
fault, but  it's certainly not expected behavior.

** Summary changed:

- Ubuntu patches to nautilus get randomly reverted again and again
+ Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus 
restart

** Description changed:

+ UPDATE: see comment 2
+ 
  From time to time, these two bugs resurface, which were fixed ages ago:
  
  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722
  https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985
  
  and also: the font type and/or size in Nautilus changes to a smaller and
  less readable font.
- 
  
  The three things always reappear at once.
  
  Then everything goes back to expected; I'm not sure if that's when I get
  some new updates installed or when I just reboot.
  
  It seems to me that all these issues are things that got changed
  upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers
  have some more common sense than the Nautilus developers.
  
- I don't know if 
+ I don't know if
  (a) sometimes someone forgets to apply some patches, and an unpatched version 
slips into Ubuntu's packages until somebody corrects it, or
  (b) some configuration gets randomly lost/changed and then restored/changed 
back on reboot.
  
  Either way, it's f***ing annoying.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 15 18:25:09 2018
  GsettingsChanges:
-  b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
-  b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'"
-  b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
-  b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
+  b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
+  b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'"
+  b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
+  b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1799 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Restarting unity-settings-daemon screws up Nautilus settings, needs
  Nautilus restart

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

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

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
Bug #1777848

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

Title:
  gnome-screensaver-command --lock starts the daemon

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

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

[Bug 1777848] Re: screen never locks

2018-09-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  screen never locks

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

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

[Bug 1777848] Re: screen never locks

2018-09-16 Thread Jarno Suni
gnome-screensaver-command --lock
does not work, but exits with 0 even if gnome-screensaver is running.

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

Title:
  screen never locks

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

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

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
And in 18.04 it is unable to start the lock even if the daemon is
running, and still exits with 0, so it is badly broken.

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

Title:
  gnome-screensaver-command --lock starts the daemon

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

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

[Bug 1536237] Re: gnome-screensaver-command --lock starts the daemon

2018-09-16 Thread Jarno Suni
Oddly in Xenial, where gnome-screensaver is 3.6.1-7ubuntu4 the bug
occurs, but in 18.04, where the version is 3.6.1-8ubuntu3, it does not
launch the daemon, but exits with 0 without locking.

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

Title:
  gnome-screensaver-command --lock starts the daemon

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

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

[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices

2018-09-16 Thread mirohe
I am the same problem that 
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1753525/comments/34

My device is ctl-4100-s no styp¡lus is detected, but tablet is detected.
Mi SO is Debian 9

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

Title:
  Wacom tablet not recognized in Settings > Devices

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

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

[Bug 1765776] Re: nautilus closes in other locations by middle-click

2018-09-16 Thread Marc Peña
I've installed version 3.26.4-0~ubuntu18.04.1 and nautilus did not crash
when middle clicking the computer in "Other locations".

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  nautilus closes in other locations by middle-click

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

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

[Bug 1788036] Re: nautilus crashed with SIGSEGV in tcache_get()

2018-09-16 Thread Martin Dauskardt
*** This bug is a duplicate of bug 1786650 ***
https://bugs.launchpad.net/bugs/1786650

I also see the same segfault showing "tcache_get (tc_idx=0) at
malloc.c:2943" when I use Thunar 1.8.1 on Xubuntu 18.04

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

Title:
  nautilus crashed with SIGSEGV in tcache_get()

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

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