[Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor

2019-06-11 Thread Steven Wolf
@ruediger.kupper
It is still definitely present on 18.04.  All apps open in the secondary 
monitor of all workspaces collapse onto the secondary monitor when the super 
key is pushed for the activity overview (but go back to their original 
workspaces when you push it again.)

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

Title:
  Ubuntu 18.04 Workspaces only change on primary monitor

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

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

[Bug 1759113] Re: evolution doesn't sync recurring events created on another device in exchange calendar

2019-02-14 Thread Steven Wolf
No, it is not a problem on 18.04.  I don't currently have a 16.04
system, so I can't test the bug anymore either.  I would be fine with
closing the bug...

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

Title:
  evolution doesn't sync recurring events created on another device in
  exchange calendar

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

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

[Bug 1759113] Re: evolution doesn't sync recurring events created on another device in exchange calendar

2018-04-03 Thread Steven Wolf
** Summary changed:

- evolution doesn't sync recurring events created on another device
+ evolution doesn't sync recurring events created on another device in exchange 
calendar

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

Title:
  evolution doesn't sync recurring events created on another device in
  exchange calendar

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

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

[Bug 1759113] Re: evolution doesn't sync recurring events created on another device

2018-04-03 Thread Steven Wolf
UPDATE:  I've tried removing and re-installing my Exchange account from
Evolution, hoping that it might refresh the calendar.  This has done
nothing.

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

Title:
  evolution doesn't sync recurring events created on another device

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

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

[Bug 1759113] [NEW] evolution doesn't sync recurring events created on another device

2018-03-26 Thread Steven Wolf
Public bug reported:

My Exchange calendar does not sync *recurring* events that were created
on other devices.

$ lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04

$ apt-cache policy evolution
evolution:
  Installed: 3.18.5.2-0ubuntu3.2
  Candidate: 3.18.5.2-0ubuntu3.2
  Version table:
 *** 3.18.5.2-0ubuntu3.2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.18.5.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

$ apt-cache policy evolution-ews
evolution-ews:
  Installed: 3.18.5-1ubuntu1
  Candidate: 3.18.5-1ubuntu1
  Version table:
 *** 3.18.5-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.18.5-1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

Dr. Google led me to a debugging command (below).  The output is
attached.

EWS_DEBUG=2 /usr/lib/evolution/evolution-calendar-factory -w &

** Affects: evolution-ews (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "log.txt"
   https://bugs.launchpad.net/bugs/1759113/+attachment/5091738/+files/log.txt

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

Title:
  evolution doesn't sync recurring events created on another device

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

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

[Bug 1517688] Re: icedtea crashes upon opening applet

2016-04-01 Thread Steven Wolf
I'm using a different package rather than icedtea.  OpenJDK integrates
through firefox just fine.  I've been doing the same thing to VPN into
my workplace.  Go to the OpenJDK website to find out more:

http://openjdk.java.net/

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

Title:
  icedtea crashes upon opening applet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1517688/+subscriptions

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


[Bug 1517688] Re: icedtea crashes upon opening applet

2016-01-29 Thread Steven Wolf
I have uninstalled icedtea and am now running everything through
OpenJDK.  That is working. (Though, if I go to java.com and verify my
version of java, it says that it is NOT up to date.  But OpenJDK is the
up to date package...but that really isn't appropriate for an icedtea
bug as these are separate packages.)

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

Title:
  icedtea crashes upon opening applet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1517688/+subscriptions

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


[Bug 1517688] [NEW] icedtea crashes upon opening applet

2015-11-18 Thread Steven Wolf
Public bug reported:

System information
> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename:   wily

This was just updated earlier today

> apt-cache policy openjdk-8-jre
openjdk-8-jre:
  Installed: 8u66-b17-1
  Candidate: 8u66-b17-1
  Version table:
 *** 8u66-b17-1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ wily-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 8u66-b01-5 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages

> apt-cache policy icedtea-plugin 
icedtea-plugin:
  Installed: 1.5.2-1ubuntu2
  Candidate: 1.5.2-1ubuntu2
  Version table:
 *** 1.5.2-1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status

I went to java.com to verify my Java version and it threw an Error.  See
below:

IcedTea-Web Plugin version: 1.5.2 (1.5.2-1ubuntu2)
Wed Nov 18 20:16:47 EST 2015
net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not 
initialize applet. For more information click "more information button".
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:739)
at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:668)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:901)
Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Application Error: The 
signed JNLP file did not match the launching JNLP file. Missing Resource: 
Signed Application did not match launching JNLP File
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.verifySignedJNLP(JNLPClassLoader.java:1005)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.checkForMain(JNLPClassLoader.java:845)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.initializeResources(JNLPClassLoader.java:659)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.(JNLPClassLoader.java:277)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.createInstance(JNLPClassLoader.java:351)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:418)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:394)
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:704)
... 2 more

 Chain: 
1) at Wed Nov 18 20:13:59 EST 2015
net.sourceforge.jnlp.LaunchException: Fatal: Application Error: The signed JNLP 
file did not match the launching JNLP file. Missing Resource: Signed 
Application did not match launching JNLP File
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.verifySignedJNLP(JNLPClassLoader.java:1005)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.checkForMain(JNLPClassLoader.java:845)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.initializeResources(JNLPClassLoader.java:659)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.(JNLPClassLoader.java:277)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.createInstance(JNLPClassLoader.java:351)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:418)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:394)
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:704)
at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:668)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:901)
2) at Wed Nov 18 20:13:59 EST 2015
net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not 
initialize applet. For more information click "more information button".
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:739)
at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:668)
at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:901)
Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Application Error: The 
signed JNLP file did not match the launching JNLP file. Missing Resource: 
Signed Application did not match launching JNLP File
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.verifySignedJNLP(JNLPClassLoader.java:1005)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.checkForMain(JNLPClassLoader.java:845)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.initializeResources(JNLPClassLoader.java:659)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.(JNLPClassLoader.java:277)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.createInstance(JNLPClassLoader.java:351)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:418)
at 
net.sourceforge.jnlp.runtime.JNLPClassLoader.getInstance(JNLPClassLoader.java:394)
at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:704)
... 2 more
3) at Wed Nov 18 20:16:42 EST 2015
net.sourceforge.jnlp.LaunchException: Fatal: