[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Ivan D]

Tested on: Ubuntu 21.04
Package: evolution-data-server 3.40.1-2 (from Impish-proposed)

There aren't packages for hursuit (21.04) but I just tried the impish
(21.10) package and works.

Thanks again

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

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

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

[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Ivan D]

Tested on: Ubuntu 20.04.2 LTS
Package: evolution-data-server 3.36.5-0ubuntu1 amd64

Personal iCloud account, now is solved.

Thanks

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

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

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

[Bug 1690689] Re: Nvidia fails to create vital files

[Ivan D. Sanders]

** Description changed:

  Let me lay out my steps for you. Starting with the minimal build, I have
  238 packages. Pretty sick. So I proceed to build the system I want with
  wicd, i3, and nvidia-375. This is where the problems are.
  
  i3 doesn't start any OpenGL environment by itself. I install mesa-utils
  and mesa-common-dev and that doesn't start anything either. When I do
  glxinfo in i3 it just says could not find RGB GLX visual or fbconfig.
  When I start steam it says openglx extension not supported by display.
  
  I know, i3 is just a window manager. But my extent of linux and Ubuntu
  knowledge are running out.
  
  Side tangent -
  
  If I install gnome-core, or gnome and gnome-shell, and reboot into i3
  this problem disappears. Its like gnome installs something and runs
  something that I can't track down. But when gnome installs it,
  obviously, installs like 1000 packages with it, and that is (kind of)
  against what I'm going for.
  
  When I remove gnome / gnome-core / gnome-shell, and then autoremove
  other packages, it DOES NOT break i3, it still starts the OpenGL
  "whatever it is I need" and that is cool. But I still have a ton of
  gnome packages that the system is using and did not autoremove. I'm
  trying to get down under 1000. My best is 1012 packages.
  
- 
- Answer: the GLX extension isn't loading because... No xorg.conf and no 
gpu-manager.conf files exist.
- 
+ Answer: the GLX extension isn't loading because... No xorg.conf and no
+ gpu-manager.conf files exist.
  
  SOLUTION
  
- nvidia needs to install 2 files,
+ nvidia needs to install 2 files, AND user needs to install ubuntu-
+ drivers-common
  
  /etc/X11/xorg.conf
  
- /etc/init/gpu-manager.conf
+ /etc/init/gpu-manager.conf (this file is created by gpu-manager
+ installed by ubuntu-drivers-common)
  
  The following is the contents of my files, for those of you running
  optimus systems with hybrid graphics. For those searching, I am running
  a G551, aka Asus ROG GL551 etc... with Nvidia 960m
  
  So here is how you fix it.
  
  You need those two files. Here are mine:
  
  /etc/X11/xorg.conf
  
  Section "ServerLayout"
  Identifier "layout"
  Screen 0 "nvidia"
  Inactive "intel"
  EndSection
  
  Section "Device"
  Identifier "intel"
  Driver "modesetting"
  BusID "PCI:0@0:2:0"
  Option "AccelMethod" "None"
  EndSection
  
  Section "Screen"
  Identifier "intel"
  Device "intel"
  EndSection
  
  Section "Device"
  Identifier "nvidia"
  Driver "nvidia"
  BusID "PCI:1@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection
  
  Section "Screen"
  Identifier "nvidia"
  Device "nvidia"
  Option "AllowEmptyInitialConfiguration" "on"
  Option "IgnoreDisplayDevices" "CRT"
  EndSection
  
  /etc/init/gpu-manager.conf
  
  start on (starting lightdm
    or starting gdm
    or starting kdm
    or starting xdm
    or starting lxdm)
  task
  exec gpu-manager --log /var/log/gpu-manager.log
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-375 375.66-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Sun May 14 20:25:59 2017
  SourcePackage: nvidia-graphics-drivers-375
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nvidia fails to create vital files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1690689/+subscriptions

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

[Bug 1690689] Re: Nvidia fails to create vital files

[Ivan D. Sanders]

** Description changed:

  Let me lay out my steps for you. Starting with the minimal build, I have
  238 packages. Pretty sick. So I proceed to build the system I want with
  wicd, i3, and nvidia-375. This is where the problems are.
  
  i3 doesn't start any OpenGL environment by itself. I install mesa-utils
  and mesa-common-dev and that doesn't start anything either. When I do
  glxinfo in i3 it just says could not find RGB GLX visual or fbconfig.
  When I start steam it says openglx extension not supported by display.
  
  I know, i3 is just a window manager. But my extent of linux and Ubuntu
  knowledge are running out.
  
+ Side tangent -
+ 
  If I install gnome-core, or gnome and gnome-shell, and reboot into i3
  this problem disappears. Its like gnome installs something and runs
  something that I can't track down. But when gnome installs it,
  obviously, installs like 1000 packages with it, and that is (kind of)
  against what I'm going for.
  
  When I remove gnome / gnome-core / gnome-shell, and then autoremove
  other packages, it DOES NOT break i3, it still starts the OpenGL
  "whatever it is I need" and that is cool. But I still have a ton of
  gnome packages that the system is using and did not autoremove. I'm
  trying to get down under 1000. My best is 1012 packages.
+ 
+ 
+ Answer: the GLX extension isn't loading because... No xorg.conf and no 
gpu-manager.conf files exist.
+ 
  
  SOLUTION
  
  nvidia needs to install 2 files,
  
  /etc/X11/xorg.conf
  
  /etc/init/gpu-manager.conf
  
  The following is the contents of my files, for those of you running
  optimus systems with hybrid graphics. For those searching, I am running
  a G551, aka Asus ROG GL551 etc... with Nvidia 960m
  
  So here is how you fix it.
  
  You need those two files. Here are mine:
  
  /etc/X11/xorg.conf
  
  Section "ServerLayout"
- Identifier "layout"
- Screen 0 "nvidia"
- Inactive "intel"
+ Identifier "layout"
+ Screen 0 "nvidia"
+ Inactive "intel"
  EndSection
  
  Section "Device"
- Identifier "intel"
- Driver "modesetting"
- BusID "PCI:0@0:2:0"
- Option "AccelMethod" "None"
+ Identifier "intel"
+ Driver "modesetting"
+ BusID "PCI:0@0:2:0"
+ Option "AccelMethod" "None"
  EndSection
  
  Section "Screen"
- Identifier "intel"
- Device "intel"
+ Identifier "intel"
+ Device "intel"
  EndSection
  
  Section "Device"
- Identifier "nvidia"
- Driver "nvidia"
- BusID "PCI:1@0:0:0"
- Option "ConstrainCursor" "off"
+ Identifier "nvidia"
+ Driver "nvidia"
+ BusID "PCI:1@0:0:0"
+ Option "ConstrainCursor" "off"
  EndSection
  
  Section "Screen"
- Identifier "nvidia"
- Device "nvidia"
- Option "AllowEmptyInitialConfiguration" "on"
- Option "IgnoreDisplayDevices" "CRT"
+ Identifier "nvidia"
+ Device "nvidia"
+ Option "AllowEmptyInitialConfiguration" "on"
+ Option "IgnoreDisplayDevices" "CRT"
  EndSection
- 
  
  /etc/init/gpu-manager.conf
  
  start on (starting lightdm
-   or starting gdm
-   or starting kdm
-   or starting xdm
-   or starting lxdm)
+   or starting gdm
+   or starting kdm
+   or starting xdm
+   or starting lxdm)
  task
  exec gpu-manager --log /var/log/gpu-manager.log
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-375 375.66-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  CurrentDesktop: i3
  Date: Sun May 14 20:25:59 2017
  SourcePackage: nvidia-graphics-drivers-375
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Nvidia fails to create vital files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1690689/+subscriptions

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

[Bug 1690689] [NEW] Nvidia fails to create vital files

[Ivan D. Sanders]

Public bug reported:

Let me lay out my steps for you. Starting with the minimal build, I have
238 packages. Pretty sick. So I proceed to build the system I want with
wicd, i3, and nvidia-375. This is where the problems are.

i3 doesn't start any OpenGL environment by itself. I install mesa-utils
and mesa-common-dev and that doesn't start anything either. When I do
glxinfo in i3 it just says could not find RGB GLX visual or fbconfig.
When I start steam it says openglx extension not supported by display.

I know, i3 is just a window manager. But my extent of linux and Ubuntu
knowledge are running out.

If I install gnome-core, or gnome and gnome-shell, and reboot into i3
this problem disappears. Its like gnome installs something and runs
something that I can't track down. But when gnome installs it,
obviously, installs like 1000 packages with it, and that is (kind of)
against what I'm going for.

When I remove gnome / gnome-core / gnome-shell, and then autoremove
other packages, it DOES NOT break i3, it still starts the OpenGL
"whatever it is I need" and that is cool. But I still have a ton of
gnome packages that the system is using and did not autoremove. I'm
trying to get down under 1000. My best is 1012 packages.

SOLUTION

nvidia needs to install 2 files,

/etc/X11/xorg.conf

/etc/init/gpu-manager.conf

The following is the contents of my files, for those of you running
optimus systems with hybrid graphics. For those searching, I am running
a G551, aka Asus ROG GL551 etc... with Nvidia 960m

So here is how you fix it.

You need those two files. Here are mine:

/etc/X11/xorg.conf

Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidia"
Inactive "intel"
EndSection

Section "Device"
Identifier "intel"
Driver "modesetting"
BusID "PCI:0@0:2:0"
Option "AccelMethod" "None"
EndSection

Section "Screen"
Identifier "intel"
Device "intel"
EndSection

Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:1@0:0:0"
Option "ConstrainCursor" "off"
EndSection

Section "Screen"
Identifier "nvidia"
Device "nvidia"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection


/etc/init/gpu-manager.conf

start on (starting lightdm
  or starting gdm
  or starting kdm
  or starting xdm
  or starting lxdm)
task
exec gpu-manager --log /var/log/gpu-manager.log

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-375 375.66-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu7
Architecture: amd64
CurrentDesktop: i3
Date: Sun May 14 20:25:59 2017
SourcePackage: nvidia-graphics-drivers-375
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Nvidia fails to create vital files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1690689/+subscriptions

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

[Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA

[Ivan D. Sanders]

So I think I managed to fix this bug with

systemctl enable bluetooth

then reboot. I don't seem to have the problem anymore.

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

Title:
  Bluetooth doesn't work on ASUS Zenbook UX301LAA

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

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

[Bug 1581814] Re: can't start bluetooth

[Ivan D. Sanders]

I think the solution to this bug is

systemctl enable bluetooth

You have to enter your password 4-5 times and then reboot. It worked for
me. can someone else try it to confirm on Asus laptops with this bug?

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

Title:
  can't start bluetooth

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

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

[Bug 1628478] Re: Mir servers crash when using the Nvidia driver

[Ivan D. Sanders]

I can confirm that this big still exists with Nvidia 378.13 and Unity 8
in Ubuntu 16.10 as of today.

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

Title:
  Mir servers crash when using the Nvidia driver

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

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

[Bug 1628478] Re: Mir servers crash when using the Nvidia driver

[Ivan D. Sanders]

This is indeed a duplicate of my new bug:
https://bugs.launchpad.net/bugs/1643420

Please close one of them,  I believe the one I linked is newer.

Confirmed again today with newest updates and proprietary  driver 375...

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

Title:
  Mir servers crash when using the Nvidia driver

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

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

[Bug 1643420] Re: Unity 8 freezes after attempted log on

[Ivan D. Sanders]

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


Graphics Controller: NVIDIA® GeForce® GTX 960M (4GB) GDDR5 (Maxwell) w/ 
Optimus™ Technology
Processor: 6th Generation Intel® Mobile Core i7-6700HQ Skylake Processor
Chipset: Intel® Mobile HM170 Express Chipset

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

Title:
  Unity 8 freezes after attempted log on

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1643420/+subscriptions

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

[Bug 1643420] [NEW] Unity 8 freezes after attempted log on

[Ivan D. Sanders]

Public bug reported:

When I switch to Unity 8 in the lock screen in Ubuntu 17.04, and try to
log on the system freezes. I can move my mouse, but I do very little.

I can shutdown and restart, surprisingly, but that is about it.

This is the freshest install of 17.04. I know, its full of bugs and
early, but lets figure this one out together!

I need some help from you, what logs and stuff do you need? What do you
need from me? Thanks in advance.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8 8.14+17.04.20161109-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 20 23:45:07 2016
InstallationDate: Installed on 2016-11-18 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161118)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Unity 8 freezes after attempted log on

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

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

[Bug 1565973] Re: Unity 8 freezes after log on

[Ivan D. Sanders]

I am having this issue right now. I am willing to work with you to
resolve it,  just need instructions...

** Changed in: unity8 (Ubuntu)
   Status: Expired => New

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

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

Title:
  Unity 8 freezes after log on

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

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

[Bug 1587555] Re: Installer crashed during installation

[Ivan D. Sanders]

** Attachment added: "Upgraded from Ubuntu 16.04 to 16.10 using: sudo 
do-release-upgrade -d"
   
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555/+attachment/4680046/+files/Screenshot%20from%202016-06-08%2017-27-18.png

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

Title:
  Installer crashed during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555/+subscriptions

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

[Bug 1587555] Re: Installer crashed during installation

[Ivan D. Sanders]

Worked for me with regular Ubuntu (Unity).

username@machine_name:~$ uname -r
4.4.0-23-generic
username@machine_name:~$ uname -a
Linux machine_name 4.4.0-23-generic #41-Ubuntu SMP Mon May 16 23:04:25 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
username@machine_name:~$

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

Title:
  Installer crashed during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555/+subscriptions

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

[Bug 1587555] Re: Installer crashed during installation

[Ivan D. Sanders]

So this is a work around:

Install Ubuntu Desktop 16.04.

Code:

# sudo do-release-upgrade -d

That will upgrade you to 16.10. This does not fix the bug, but it works
to get 16.10.

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

Title:
  Installer crashed during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555/+subscriptions

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

[Bug 1588887] [NEW] yakkety yak crashed after retrieving 99 files, during install.

[Ivan D. Sanders]

Public bug reported:

yakkety yak crashed after retrieving 99 files, during install... I don't
know more.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CasperVersion: 1.376
Date: Fri Jun  3 11:46:42 2016
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160601)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-16.10.1 ubuntu yakkety

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

Title:
  yakkety yak crashed after retrieving 99 files, during install.

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

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

[Bug 951000] Re: disable guest session screen lock using gsettings

[Ivan D Vasin]

a similar issue exists with Kubuntu 12.10.  lightdm offers a guest session, but
  * Kickoff's Leave menu offers a Lock action that locks the session, and
  * when the screensaver activates, it locks the session.
in both cases, the lock screen's unlock dialog shows an apparently 
auto-generated username (e.g. "guest-iW6OvM") and requires a password to unlock 
the session.  as a result, the user is stuck in the lock screen.

the unlock dialog offers a "Switch User..." action, which subsequently
offers to "Start New Session".  but using this to start a "new" guest
session actually just switches to the existing session, which is still
locked.

a quick workaround is to restart lightdm from the console (ctrl+alt+f1,
log in as an admin user, ``sudo service lightdm restart``).  however,
the previous guest session is lost as a result, along with any work that
was unsaved in it.  also, it shouldn't be expected that a guest user has
access to an admin account.

glancing over the suggestions in the comments here, it looks like the
fix may or may not be specific to the session manager, depending on the
chosen approach.  i see suggestions that appear to be specific to GNOME
(via GSettings); my Kubuntu installation has GSettings, but i have no
idea whether/how it is used by Kubuntu.

is it appropriate to address this in this bug, or should i create a new
one specifically regarding KDE guest sessions?

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

Title:
  disable guest session screen lock using gsettings

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

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

[Bug 760632] Re: Resizing Konsole crashes the whole system

[Ivan D Vasin]

@Yusef:

at the risk of being a bit off-topic, i'll mention that i have a very
similar experience on a Gentoo system with a GeForce GTX 465 using the
275.09.07 driver.  i also have similar problems in Windows 7 in some
graphics-intensive games and Flash videos with the same card, especially
with the 275.33 driver (less so with the 270.61 or the 275.50).  at some
point, the whole system simply freezes; in Windows, the screen goes
black for about 10 seconds, then reboots.

on a different system with a GeForce 330M, i don't have these issues,
and the 275.09.04 and 275.09.07 drivers both resolve the specific issue
in this bug (freezing during Konsole resize).

do you have a GTX 400 series card?  if so, try a card from a different
series.  perhaps there's something wrong with these.  i plan on doing
the same when i find time to borrow my roommate's GTX 260.

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

Title:
  Resizing Konsole crashes the whole system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/760632/+subscriptions

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

[Bug 760632] Re: Resizing Konsole crashes the whole system

[Ivan D Vasin]

i've seen a number of people recommend installing the latest drivers
from ppa:philip5/extra, but i'd like to caution wary users (and eager
newbie users) against doing so by adding the PPA to their apt sources.
doing so may cause a subsequent system-wide upgrade to upgrade more
packages than you bargained for.  then, if you later remove the PPA from
your apt sources, apt will not revert those packages to the
corresponding ones from the Ubuntu repos--they'll stay at the PPA's
versions until Ubuntu's versions exceed them.  to fully revert the
packages, (as far as i know) you'll need to use something like ppa-purge
.

to cherry-pick the nvidia-graphics package from the PPA, you can grab
the appropriate .deb package directly from the PPA's web site by
following the "View package details" link above the package list.  this
is the route i chose to resolve this bug on my systems.  this [1] should
be the appropriate .deb for 64-bit systems, and this [2] should be the
one for 32-bit systems.

[1] 
https://launchpad.net/~philip5/+archive/extra/+build/2552862/+files/nvidia-current_275.09.04-natty%7Eppa1_amd64.deb
[2] 
https://launchpad.net/~philip5/+archive/extra/+build/2552863/+files/nvidia-current_275.09.04-natty%7Eppa1_i386.deb

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

Title:
  Resizing Konsole crashes the whole system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/760632/+subscriptions

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

[Bug 727487] Re: akonadi libgcal and googledata

[Ivan D Vasin]

according to the conclusions reached in KDE bug 264861 [1], this is a
packaging bug.  building and installing these same versions from source
--even using a simple dpkg-buildpackage call for each one--appears to
fix the problem.

[1] https://bugs.kde.org/show_bug.cgi?id=264861

** Bug watch added: KDE Bug Tracking System #264861
   http://bugs.kde.org/show_bug.cgi?id=264861

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

Title:
  akonadi libgcal and googledata

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