[Bug 1913957] [NEW] internet slows frames start dropping and then the entire system restarts

[Robert M Shiles]

Public bug reported:

I recently installed Ubuntu 20.04, the system will slow significantly,
start dropping frames, slowing internet speeds, and finally randomly
restart. once it restarts it enters this cycle where it will keep
restarting multiple times before it reaches the log in screen. This
occurred even when I was first installing it on this machine. Windows 10
worked fine on the system however I no longer have it installed because
it was corrupted during the Linux installation process. I have since
reinstalled ubuntu multiple times all of which have been quite arduous
with the system crashing multiple times before I could get through a
complete installation.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.30
ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 31 12:35:18 2021
InstallationDate: Installed on 2021-01-27 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade focal

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

Title:
  internet slows frames start dropping and then the entire system
  restarts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1913957/+subscriptions

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

[Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list

[Robert M. Muncrief]

This bug is marked as "Fix Released" but after years of running Manjaro
I decided to give Ubuntu a try again with Disco Dingo 19.04 and it was
simply impossible because it still exists. I could get past the initial
error, and Ubuntu thought it was installed, but trying to boot just
output the error message on an otherwise black screen.

The message is the same as everyone else is getting:
Couldn't get size: 0x800e
MODSIGN: Couldn't get UEFI db list
Couldn't get size: 0x800e

So unfortunately I just had to reinstall Manjaro so I could get back to
work. By the way this is the reason I left Ubuntu in the first place. If
you want to run a years old OS with years old software you can use an
LTS release that's fairly stable. But if you want a current OS and
current software interim Ubuntu releases are most often disasters, right
up until it's life cycle is over.

And then the nightmare begins all over again.

But if Ubuntu is ever able to maintain a distribution that's three
months or less behind mainline I'll give it a try again. It would be
nice to use .deb packages without translation. It's a shame, and I
really don't understand. Manjaro and other rolling releases have nowhere
near the problems Ubuntu has keeping up to date. Their only downside is
that for the most part no one supports them, so you have to do a lot of
customization and compiling of third party software.

Anyway, good luck guys and gals. Despite my complaining I wish the best
for Ubuntu.

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

Title:
  MODSIGN: Couldn't get UEFI db list

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

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

[Bug 1727503] [NEW] package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade: package libpam-systemd:amd64 is already installed and configured

[Robert M Price]

Public bug reported:

appears to be installed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-systemd:amd64 229-4ubuntu20
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports: 600:0:116:300648:2017-10-25 14:59:54.335597515 -0500:2017-10-25 
14:59:55.335597515 -0500:/var/crash/libpam-systemd:amd64.0.crash
Date: Wed Oct 25 14:59:55 2017
DuplicateSignature:
 package:libpam-systemd:amd64:229-4ubuntu20
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package libpam-systemd:amd64 (--configure):
  package libpam-systemd:amd64 is already installed and configured
ErrorMessage: package libpam-systemd:amd64 is already installed and configured
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: dpkg
Title: package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade: 
package libpam-systemd:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package libpam-systemd:amd64 229-4ubuntu20 failed to install/upgrade:
  package libpam-systemd:amd64 is already installed and configured

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

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

[Bug 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

[Robert M. Muncrief]

I tested libepoxy0_1.3.1-1ubuntu0.16.04.2 amd64 and i386 as requested
and it works without error. My system is Xubuntu 16.04.2 with kernel
4.9.35-lowlatency. Thank you for your excellent work!

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

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

Title:
  [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO

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

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

[Bug 1698233] Re: New libepoxy0 causes hang at boot for AMDGPU-PRO

[Robert M. Muncrief]

I tried the 1.4.3-0ubuntu2 version as well and it also reintroduced the
black screen hang on boot for me. I reverted back to
1.3.1-1ubuntu1.16.04.2.

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

Title:
  New libepoxy0 causes hang at boot for AMDGPU-PRO

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

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

[Bug 1698233] Re: New libepoxy0 causes hang at boot

[Robert M. Muncrief]

@LocutusOfBorg, this seems to work perfectly. I tried a few iterations
of playing No Man's Sky, browsing with Chrome, and playing video with
VLC and everything worked as expected. Thank you for the quick fix.

If anyone else needs this update before it's in the main repositories
execute the following (substituting whatever text editor you use):

sudo mousepad /etc/apt/sources.list

Add:
deb http://ppa.launchpad.net/costamagnagianfranco/locutusofborg-ppa/ubuntu 
xenial main

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 4E9F5DD9
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 1BCB19E03C2A1859
sudo apt-get update
sudo apt-get install libepoxy0 libepoxy-dev libepoxy0:i386  libepoxy-dev:i386

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

Title:
  New libepoxy0 causes hang at boot

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

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

[Bug 1698233] Re: New libepoxy0 causes hang at boot

[Robert M. Muncrief]

The Mesa drivers only support OpenGL 4.5 Core mode, they don't support
OpenGL 4.5 Compatibility mode. It's odd but for some reason they only
support OpenGL 3.3 Compatibility mode, and the developers have stated
they don't intend on changing it. So games and other software that
require higher Compatibility modes will never run on Mesa.

There are some environment variables, MESA_GLSL_VERSION_OVERRIDE and
MESA_GL_VERSION_OVERRIDE, that make the drivers report a higher
compatibility mode but since the underlying functionality is still
missing they don't work.

In any case I have a Sapphire Nitro R9-390 so I'm trying to work out a
deal a crypto-miner to exchange it for an Nvidia GPU. Unfortunately AMD
is only fully functional for crypto-mining under Linux at this time, and
since AMDGPU-PRO will be a mess for the next few years and the open
source drivers will never be fully functional I'm giving up on AMD.
Thank you for your help but I've lived with a crippled GPU for almost a
year now and I have to acknowledge there's no viable option left other
than surrender. It's not Ubuntu's fault, AMD simply abandoned its loyal
customers.

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

Title:
  New libepoxy0 causes hang at boot

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

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

[Bug 1698233] Re: New libepoxy0 causes hang at boot

[Robert M. Muncrief]

@LocutusOfBorg, I tried adding your repository again today and received
this error with sudo apt-get update:

Err:33 
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+packages
 xenial/main amd64 Packages
  404  Not Found

I don't know if this occurred before, but in any case I downloaded
libepoxy-dev, libepoxy-dev:i386, libepoxy0, and libepoxy0:i386 from your
repository and manually installed them with gdebi. I then placed the
packages on hold and did a sudo apt-get update and sudo apt-get dist-
upgrade.

After this the system booted without hanging, so I played No Man's Sky
under wine for a few moments, as this is one of the things that requires
OpenGL 4.5 compatibility mode. The game played fine, but after exiting
it and Steam I tried opening Chrome and the system froze and the screen
turned black.

However I rebooted the system and tried the same thing again a few times
and it didn't crash. So I suspect there's some type of memory corruption
that's difficult to replicate, but can't know for sure. In any case
whatever you did solved the hang at boot problem, so you're correct
about whatever you thought the problem was. Thank you for your work, and
I appreciate you looking into a problem only a few of us have.

As to where to go from here, I don't know. The crux of the problem is
that AMD abandoned their fglrx drivers before a replacement was ready,
and threw those of us who had just bought $300+ graphics cards off the
cliff. I'd like to abandon them now and get an Nvidia GPU, but at this
moment there's a problem procuring medium to high end GPUs, of any
brand, because of digital currency mining.

So if it's not a lot of effort and you know what the problem is and can
fix it permanently, that would be awesome. On the other hand I know
development resources are limited and I won't blame you if you decide
it's not worth the effort because of the very few people it affects, and
the fact that it's AMD's fault not Ubuntu's.

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

Title:
  New libepoxy0 causes hang at boot

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

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

[Bug 1698233] Re: New libepoxy0 causes hang at boot

[Robert M. Muncrief]

I removed the libepoxy0 package holds, added the LocutusOfBorg
repository, and did an apt-get update and apt-get dist-upgrade. However
my system still hung on reboot. If I did something wrong please let me
know.

Also the problem only occurs with AMDGPU-PRO, I should have been clear
about that. Unfortunately I can't use the open source mesa though
because I need OpenGL 4.5 compatibility mode and mesa doesn't support
anything over 3.3. The developers say they don't have the resources to
implement it, so anyone using Ubuntu who needs it will always have to
use AMDGPU-PRO.

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

Title:
  New libepoxy0 causes hang at boot

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

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

[Bug 1698233] Re: New libepoxy0 causes hang at boot

[Robert M. Muncrief]

Yes Micheal, that's all anyone confronted with this bug needs to do
initially so they can boot.

After booting they should also open a terminal and issue one of the
following commands:

For amd64 systems:
sudo apt-mark hold libepoxy-dev libepoxy0 libepoxy0:i386

For i386 systems:
sudo apt-mark hold libepoxy-dev libepoxy0

This will prevent libepoxy0 from being updated until this bug is fixed.
Note that if you use programs like Synaptic libepoxy0 needs to be locked
there as well.

And by the way, the only reason I wasn't able to use recovery mode
initially was because I didn't know libepoxy0 was the culprit. About 15
updates appeared together, with several of them being for Mir which is
what I initially suspected caused the problem. Since I wasn't sure what
was wrong it took awhile for me to whittle it down to libepoxy0.

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

Title:
  New libepoxy0 causes hang at boot

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

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

[Bug 1698233] [NEW] New libepoxy0 causes hang at boot

[Robert M. Muncrief]

Public bug reported:

When updating my Xubuntu 16.04.2 system today the upgrade from libepoxy0
1.3.1-1 to libepoxy0 1.3.1-1ubuntu0.16.04.1 caused my system to hang
right before the login screen.

Unfortunately since this was a complete system lock up I can't provide
any logs as I had to restore the entire root partition from backup.
Since I can't get system recovery mode to work (it's been broken for a
few years and times out within two minutes) it doesn't give me enough
time gather any logs before it exits. I understand the system recovery
problem is known, but I've tried all the solutions I could over the
years, on multiple systems, and just can't get it to work without timing
out anymore.

In any case I verified the problem was libepoxy0 by applying all the
available updates except libexpoxy0 and rebooting without any problems.
I then allowed the upgrade of libepoxy0, libepoxy0:i386, and libeepoxy-
dev and the system hung at boot as previously described. I went through
the same procedure twice to confirm.

I'm running kernel 4.9.31-040931-lowlatency with AMDGPU-PRO 16.50
patched drivers, with all system updates. If you need more information
please contact me and I'll get you anything I can. But as I said, since
the system locks up I'm not sure what else I can garner.

lsb_release -rd:
Description:Ubuntu 16.04.2 LTS
Release:16.04

apt-cache policy libepoxy0:
libepoxy0:
  Installed: 1.3.1-1
  Candidate: 1.3.1-1ubuntu0.16.04.1
  Version table:
 1.3.1-1ubuntu0.16.04.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 1.3.1-1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  New libepoxy0 causes hang at boot

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

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

[Bug 1168742] Re: [udev] Disks are not unmounted when physical eject button is used

[Robert M. Muncrief]

I can confirm this problem still exists with Xubuntu 16.04 x64. I hope
it's fixed someday. It's difficult to win Windows users over when common
things like this don't work, it's very confusing for them and they just
want me to reinstall Windows :(

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

Title:
  [udev] Disks are not unmounted when physical eject button is used

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

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

[Bug 1425000] Re: Cannot set right monitor as primary in dual monitor configuration

[Robert M. Muncrief]

I can confirm the same problem exists with Xubuntu x64 16.04 as well.
However I can also confirm that this has been a problem with all Ubuntu
flavors for many years.

The difference now is that nothing can be done on the user side to fix
it. After all these years I'd become quite adept at editing display.xml
and monitor.xml files, xorg.conf files, etc. but now none of that works.
The only thing I haven't tried is changing Compiz settings, but that's
because Xubuntu doesn't run Compiz by default, and people running Compiz
have already reported that it can't be fixed their anyway.

I know the developers work hard and always have their plates full, but
if they could at least fix it enough that we could edit conf files again
it would be great.

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

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

Title:
  Cannot set right monitor as primary in dual monitor configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1425000/+subscriptions

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

[Bug 1512120] Re: thunar crashes on file renaming

[Robert M. Muncrief]

This bug still exists in Xubuntu 16.04.1 amd64 as of today. Thunar is
version 1.6.10-2ubuntu1, and the system has all current updates applied.
I installed Xubuntu about a week ago and Thunar crashes almost every
time I try to rename a file with it. I've started using mv from the
terminal to avoid further crashes.

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

Title:
  thunar crashes on file renaming

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

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

[Bug 1605346] [NEW] package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Robert M. Muncrief]

Public bug reported:

I keep my database in a different directory for contents that are backed
up. To accomplish that I modify /etc/mysql/mysql.conf.d/mysqld.cnf,
/etc/apparmor.d/usr.sbin.mysqld, and /usr/share/mysql/mysql-systemd-
start.

When the software update ran it crashed instead of asking me if I wanted
to keep or merge the modified configuration files contents.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.13-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Jul 21 10:51:09 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-07-16 (5 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Logs.var.log.daemon.log:
 
Logs.var.log.mysql.error.log: 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['debian-5.7.flag']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=235d51b1-bd4b-4554-a15d-0d8eb362b7f6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.usr.sbin.mysqld: [modified]
modified.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2016-07-16T13:08:23.896390
mtime.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: 2016-07-16T13:07:15.637998

** Affects: mysql-5.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package mysql-server-5.7 5.7.13-0ubuntu0.16.04.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1605346/+subscriptions

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

Re: [Bug 1603151] Re: systemctl isolate anyname.target not working

[Robert M. Koretsky]

Martin:
Sounds good, thanks for the info about systemctl stop lightdm!
Robert M. Koretsky

On Sun, Jul 17, 2016 at 10:41 PM, Martin Pitt <martin.p...@ubuntu.com>
wrote:

> This is the same with "systemctl stop lightdm", btw. I'm reassigning
> this to lightdm.
>
> ** Summary changed:
>
> - systemctl isolate anyname.target not working
> + stopping lightdm ends up in an empty console, should switch to VT1
>
> ** Package changed: systemd (Ubuntu) => lightdm (Ubuntu)
>
> ** Changed in: lightdm (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: lightdm (Ubuntu)
>Status: Incomplete => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603151
>
> Title:
>   stopping lightdm ends up in an empty console, should switch to VT1
>
> Status in lightdm package in Ubuntu:
>   Triaged
>
> Bug description:
>   On Ubuntu 16.04 Cinammon, systemctl isolate multi-user.target hangs the
> system.
>   I've tried editing the multi-user.target file as a snippet, or the whole
> thing, but with no fix.
>   The system flashes a very momentary prompt to login as a single user
> without a GUI, but then the screen goes black and the system is hung.
>   Same on Linux Mint 18.
>   systemctl isolate multi-user.target works successfully on OpenSuse Leap
> 42.1, and CentOS 7, as I tested the command on these other systems to
> check. The glaring difference I noticed is that in the multi-user.target
> unit file, AllowIsolate and CanIsolate is set to yes in the other Linux
> systems, but to no in Ubuntu.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1603151/+subscriptions
>

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

Title:
  stopping lightdm ends up in an empty console, should switch to VT1

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

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

Re: [Bug 1603151] Re: systemctl isolate anyname.target not working

[Robert M. Koretsky]

Martin:
Yes, that's all that remains of this for me. But it's no big deal to hold
down Ctrl-Alt-F2 to switch to tty2.
Robert M. Koretsky

On Sun, Jul 17, 2016 at 10:40 PM, Martin Pitt <martin.p...@ubuntu.com>
wrote:

> So to summarize, the only problem is that stopping lightdm does not
> change the VT back to 1 or 2 or something sensible, but stays at 7 where
> no getty ("login:") is running so it might *appear* crashed?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603151
>
> Title:
>   stopping lightdm ends up in an empty console, should switch to VT1
>
> Status in lightdm package in Ubuntu:
>   Triaged
>
> Bug description:
>   On Ubuntu 16.04 Cinammon, systemctl isolate multi-user.target hangs the
> system.
>   I've tried editing the multi-user.target file as a snippet, or the whole
> thing, but with no fix.
>   The system flashes a very momentary prompt to login as a single user
> without a GUI, but then the screen goes black and the system is hung.
>   Same on Linux Mint 18.
>   systemctl isolate multi-user.target works successfully on OpenSuse Leap
> 42.1, and CentOS 7, as I tested the command on these other systems to
> check. The glaring difference I noticed is that in the multi-user.target
> unit file, AllowIsolate and CanIsolate is set to yes in the other Linux
> systems, but to no in Ubuntu.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1603151/+subscriptions
>

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

Title:
  stopping lightdm ends up in an empty console, should switch to VT1

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

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

Re: [Bug 1603151] Re: systemctl isolate anyname.target not working

[Robert M. Koretsky]

Martin:
After systemctl isolate multi-user.target, I could ssh into the machine.
Also, after systemctl isolate multi-user.target, then Ctrl-Alt-F2, I could
login on tty2.
Proof that the system didn't hang or crash.
I could then systemctl isolate graphical.target and was back in the
beautiful Cinnamon Desktop!
That's a fix for me.
My graphics card is whatever comes standard on the motherboard of an HP
Proliant Microserver.
I've attached the requested journal log files.
I will experiment with switching to rescue and emergency targets work as
well.
Initially, I was doing the systemctl isolate on a Mint 18 guest running in
VirtualBox. I could ssh into the VirtualBox guest, but couldn't figure out
how to use Ctrl-Alt-F2 in the guest. The above session was done on Mint 18
running on bare metal on the HP.
Thanks very much for helping to solve my problem!
Sincerely,
Robert M. Koretsky


On Sun, Jul 17, 2016 at 2:17 PM, Martin Pitt <martin.p...@ubuntu.com>
wrote:

> > The system flashes a very momentary prompt to login as a single user
> without a GUI, but then the screen goes black and the system is hung.
>
> That sounds like the command actually worked, but stopping lightdm and
> thus the graphics driver breaks the state of the graphics card. Does
> changing VTs with Ctrl-Alt-F2 work? If not, please check if you can
> still log into the system with ssh (I suppose that works), and capture
> "sudo journalctl -b > /tmp/journal.txt" and "systemctl status >
> /tmp/status.txt" and attach the files here. Also, which graphics
> driver/card are you using? Please don't file bugs direectly in
> Launchpad, use "ubuntu-bug" for this (this will automatically attach
> information about your hardware).
>
> > The glaring difference I noticed is that in the multi-user.target unit
> file, AllowIsolate and CanIsolate is set to yes in the other Linux
> systems, but to no in Ubuntu.
>
> Ubuntu does not modify the upstream unit, and it does have
> AllowIsolate=yes. "CanIsolate" does not exist.
>
> ** Changed in: systemd (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603151
>
> Title:
>   systemctl isolate anyname.target not working
>
> Status in systemd package in Ubuntu:
>   Incomplete
>
> Bug description:
>   On Ubuntu 16.04 Cinammon, systemctl isolate multi-user.target hangs the
> system.
>   I've tried editing the multi-user.target file as a snippet, or the whole
> thing, but with no fix.
>   The system flashes a very momentary prompt to login as a single user
> without a GUI, but then the screen goes black and the system is hung.
>   Same on Linux Mint 18.
>   systemctl isolate multi-user.target works successfully on OpenSuse Leap
> 42.1, and CentOS 7, as I tested the command on these other systems to
> check. The glaring difference I noticed is that in the multi-user.target
> unit file, AllowIsolate and CanIsolate is set to yes in the other Linux
> systems, but to no in Ubuntu.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1603151/+subscriptions
>


** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/1603151/+attachment/4702550/+files/journal.txt

** Attachment added: "status.txt"
   https://bugs.launchpad.net/bugs/1603151/+attachment/4702551/+files/status.txt

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

Title:
  systemctl isolate anyname.target not working

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

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

[Bug 1603151] [NEW] systemctl isolate anyname.target not working

[Robert M. Koretsky]

Public bug reported:

On Ubuntu 16.04 Cinammon, systemctl isolate multi-user.target hangs the system.
I've tried editing the multi-user.target file as a snippet, or the whole thing, 
but with no fix.
The system flashes a very momentary prompt to login as a single user without a 
GUI, but then the screen goes black and the system is hung.
Same on Linux Mint 18.
systemctl isolate multi-user.target works successfully on OpenSuse Leap 42.1, 
and CentOS 7, as I tested the command on these other systems to check. The 
glaring difference I noticed is that in the multi-user.target unit file, 
AllowIsolate and CanIsolate is set to yes in the other Linux systems, but to no 
in Ubuntu.

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

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

Title:
  systemctl isolate anyname.target not working

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

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

Re: [Bug 1573787] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package accou

[Robert M]

Thank you Paul  . I also went back to Ubuntu 16.04 with the 4.6 kernel and
its seems stable .

On Fri, May 20, 2016 at 8:38 AM, P.Johnston <1573...@bugs.launchpad.net>
wrote:

> Bruce,
> Robert,
>
> I've given up on KDE.  Too many screen artifacts in menus and text (within
> terminal).  No update, video driver, or number of reboots would fix it.  So
> I'm back to Gnome / Unity.  Plus, Gnome/Unity feels more Linux like.
>
> Thank you,
>
> Paul
>
>
>
>
> --
> Paul D. Johnston
> paul.d.johns...@gmail.com
> paul.d.johnston@mail.mil
>
> Visit my photography blog at:
> http://pj8photography.wordpress.com/
> My Flickr stream at:
> http://flic.kr/s/aHsjz15Aup
>
> On Fri, May 20, 2016 at 10:30 AM, Bruce Miller  wrote:
>
> > Workaround:
> > sudo dpkg -i --force-overwrite
> >
> /var/cache/apt/archives/kaccounts-providers_4%3a15.12.3-0ubuntu1_amd64.deb
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1583273).
> > https://bugs.launchpad.net/bugs/1573787
> >
> > Title:
> >   package kaccounts-providers (not installed) failed to install/upgrade:
> >   trying to overwrite '/etc/signon-ui/webkit-
> >   options.d/www.facebook.com.conf', which is also in package account-
> >   plugin-facebook 0.12+16.04.20160126-0ubuntu1
> >
> > Status in One Hundred Papercuts:
> >   Confirmed
> > Status in kaccounts-providers package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   Crash on exit
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 16.04
> >   Package: kaccounts-providers (not installed)
> >   ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
> >   Uname: Linux 4.4.0-21-generic x86_64
> >   ApportVersion: 2.20.1-0ubuntu2
> >   Architecture: amd64
> >   Date: Fri Apr 22 13:38:52 2016
> >   DuplicateSignature:
> >Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
> >dpkg: error processing archive
> >
> /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
> > (--unpack):
> > trying to overwrite '/usr/share/accounts/services/google-im.service',
> > which is also in package account-plugin-google
> 0.12+16.04.20160126-0ubuntu1
> >   ErrorMessage: trying to overwrite
> > '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
> > package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
> >   InstallationDate: Installed on 2016-04-22 (0 days ago)
> >   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> > (20160420.1)
> >   RelatedPackageVersions:
> >dpkg 1.18.4ubuntu1
> >apt  1.2.10ubuntu1
> >   SourcePackage: kaccounts-providers
> >   Title: package kaccounts-providers (not installed) failed to
> > install/upgrade: trying to overwrite
> > '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
> > package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
> >   UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/hundredpapercuts/+bug/1573787/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573787
>
> Title:
>   package kaccounts-providers (not installed) failed to install/upgrade:
>   trying to overwrite '/etc/signon-ui/webkit-
>   options.d/www.facebook.com.conf', which is also in package account-
>   plugin-facebook 0.12+16.04.20160126-0ubuntu1
>
> Status in One Hundred Papercuts:
>   Confirmed
> Status in kaccounts-providers package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Crash on exit
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: kaccounts-providers (not installed)
>   ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
>   Uname: Linux 4.4.0-21-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   Date: Fri Apr 22 13:38:52 2016
>   DuplicateSignature:
>Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
>dpkg: error processing archive
> /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
> (--unpack):
> trying to overwrite '/usr/share/accounts/services/google-im.service',
> which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
>   ErrorMessage: trying to overwrite
> '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
> package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
>   InstallationDate: Installed on 2016-04-22 (0 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1
>apt  1.2.10ubuntu1
>   SourcePackage: kaccounts-providers
>   Title: package kaccounts-providers (not installed) failed to
> install/upgrade: trying to overwrite
> '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
> package 

Re: [Bug 1573787] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package accou

[Robert M]

I stopped using the accounts section since, so i have not checked since
submission of the bug or any further Ubuntu regression updates . i have
installed 4.6 kernel since and a lot of pushed updates give me few days to
check it .

Robert Maultz

On Fri, May 20, 2016 at 4:29 AM, Robert Bredereck 
wrote:

> Is there any work-around known?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573787
>
> Title:
>   package kaccounts-providers (not installed) failed to install/upgrade:
>   trying to overwrite '/etc/signon-ui/webkit-
>   options.d/www.facebook.com.conf', which is also in package account-
>   plugin-facebook 0.12+16.04.20160126-0ubuntu1
>
> Status in One Hundred Papercuts:
>   Confirmed
> Status in kaccounts-providers package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Crash on exit
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: kaccounts-providers (not installed)
>   ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
>   Uname: Linux 4.4.0-21-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   Date: Fri Apr 22 13:38:52 2016
>   DuplicateSignature:
>Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
>dpkg: error processing archive
> /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
> (--unpack):
> trying to overwrite '/usr/share/accounts/services/google-im.service',
> which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
>   ErrorMessage: trying to overwrite
> '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
> package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
>   InstallationDate: Installed on 2016-04-22 (0 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1
>apt  1.2.10ubuntu1
>   SourcePackage: kaccounts-providers
>   Title: package kaccounts-providers (not installed) failed to
> install/upgrade: trying to overwrite
> '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in
> package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hundredpapercuts/+bug/1573787/+subscriptions
>

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

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

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

[Bug 1573787] [NEW] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account

[Robert M]

Public bug reported:

Crash on exit

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: kaccounts-providers (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 22 13:38:52 2016
DuplicateSignature:
 Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
  trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
InstallationDate: Installed on 2016-04-22 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: kaccounts-providers
Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kaccounts-providers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kaccounts-providers/+bug/1573787/+subscriptions

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

[Bug 1477266] [NEW] package open-iscsi 2.0.873-3ubuntu11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Robert M]

Public bug reported:

Prompted to submit bug report AS

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: open-iscsi 2.0.873-3ubuntu11
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic i686
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: i386
Date: Wed Jul 22 11:42:29 2015
DuplicateSignature: package:open-iscsi:2.0.873-3ubuntu11:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-07-14 (8 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150215)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: open-iscsi
Title: package open-iscsi 2.0.873-3ubuntu11 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: open-iscsi (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 vivid

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

Title:
  package open-iscsi 2.0.873-3ubuntu11 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1477266/+subscriptions

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

[Bug 1198442] Re: package fglrx (not installed) failed to install

[Robert M. Muncrief]

This bug occurs on Ubuntu 14.04 as well, which is what I'm running. But
for some reason the bug utility will only let me report it on this
thread.

I already knew that the Catalyst 15.2 beta drivers didn't work, that's
why I never moved to Ubuntu 15.04. The last working drivers are Catalyst
14.12. I use Cairo Dock and the 15.2 drivers cause freezing and
jittering in the dock, and random crashes elsewhere.

I accidentally installed them because I guess they've just been
backported to Ubuntu 14.04. Please remove them from the repositories
until they are officially available from AMD. I always have problems
with the pre-compiled fglrx drivers but when I compile them myself they
always work. I can't do that with the Catalyst 15.2 drivers because for
some reason only the Ubuntu developers have them. Very strange, and
unwise.

If someone wants to move these comments to a 14.04 thread for this
identical bug please do, I wasn't able to do so myself.

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

Title:
  package fglrx (not installed) failed to install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1198442/+subscriptions

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

Re: [Bug 1454907] Re: Fresh 14.10 install on TA970 motherboard with HD6450 graphics card

[Robert M. Muncrief]

On 05/14/2015 06:11 AM, Phillip Susi wrote:
 Please choose the check disc option from the boot menu to verify the
 integrity of the installation image, as well as the memtest option and
 let it run for at least 15 minutes to see if your ram has errors.


 ** Changed in: ubiquity (Ubuntu)
 Status: New = Incomplete

I'm sorry but I'd already gone ahead and tried to install 14.10 in UEFI 
mode (which I despise beyond measure) and the same media installed 14.10 
in UEFI mode. But then I had an AMD-Vi IOAPIC error in dmesg, but that's 
another issue which seems to have already been reported. So I'm back to 
trying 14.04, but grub2 failed with a can't install to target error. 
I'm about to try a 14.04 reinstall so I'll test the media and RAM now. 
The tests should still be valid even though it's 14.04. If I can't get 
14.04 to install I'll try 14.10 again with the same tests.

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

Title:
  Fresh 14.10 install on TA970 motherboard with HD6450 graphics card

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

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

[Bug 1454907] [NEW] Fresh 14.10 install on TA970 motherboard with HD6450 graphics card

[Robert M. Muncrief]

Public bug reported:

Trying to install Ubuntu 14.10 on Biostar TA970 motherboard with HD6450
graphics card and 12GB DDR3 ram.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.20.0
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CasperVersion: 1.345
Date: Wed May 13 19:27:54 2015
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.20.0 ubuntu utopic

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

Title:
  Fresh 14.10 install on TA970 motherboard with HD6450 graphics card

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

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

[Bug 1448418] Re: Logout not working in Cairo Dock

[Robert M. Muncrief]

I have the same problem as pramathesh. In addition if you enable logout
and shutdown in the main menu neither work. I have tried the various
delay start up solutions found on the Internet but none work.

There is also a problem if you attempt to use the GLX mode. The entire
dock will intermittently jerk, freeze, go back to normal, jerk, freeze,
etc. I have tried the included fglrx and fglrx-update drivers with and
without acceleration within Unity, Cairo Dock Sessions, and in Ubuntu
Mate 15.04. I am using a Radeon HD 6450 GPU. I am installing and setting
up Cairo Dock the same way I do in Ubuntu 14.04 with the same hardware
and it works perfectly. I have been attempting to use Cairo Dock since
Ubuntu 15.04 beta and the problems have been identical and consistent.

I use all of my operating systems on ESXi 5.5 with GPU, audio, and USB
pass-through so it's easy for me to switch things around and try
different scenarios. I am willing to try any tests and solutions
proposed, just let me know what you'd like to try. I'm an active
supporter and fan of Cairo Dock so I am eager to see these problems
solved so I can move on from 14.04.

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

Title:
  Logout not working in Cairo Dock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/1448418/+subscriptions

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

[Bug 1447420] [NEW] fglrx-core (not installed): fglrx-core kernel module failed to build [error: implicit declaration of function ‘__get_cpu_var’]

[Robert M. Muncrief]

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

Public bug reported:

Catalyst 14.12 will not compile for an HD 6450 card on Ubuntu Mate
15.04.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:14.501-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.19.0-15-generic
Date: Wed Apr 22 19:16:51 2015
DuplicateSignature: dkms:fglrx-core:(not 
installed):/var/lib/dkms/fglrx-core/14.501/build/2.6.x/firegl_public.c:4819:5: 
error: implicit declaration of function ‘__get_cpu_var’ 
[-Werror=implicit-function-declaration]
InstallationDate: Installed on 2015-04-23 (0 days ago)
InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Beta amd64 (20150326)
PackageVersion: (not installed)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: fglrx-installer
Title: fglrx-core (not installed): fglrx-core kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check vivid

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

Title:
  fglrx-core (not installed): fglrx-core kernel module failed to build
  [error: implicit declaration of function ‘__get_cpu_var’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1447420/+subscriptions

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

[Bug 1431068] Re: fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to build [error: implicit declaration of function ‘__get_cpu_var’]

[Robert M. Muncrief]

AMD Catalyst 14.12 drivers will not compile on Ubuntu 15.04. I am using
an HD 6450 and can compile the drivers fine on 14.04 LTS. The fglrx beta
drivers included with 15.04 are very buggy and unusable with cairo-dock
so it is critical to able to compile the 14.12 drivers.

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

Title:
  fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed
  to build [error: implicit declaration of function ‘__get_cpu_var’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1431068/+subscriptions

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

[Bug 859101] Re: fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete file: .../linux/version.h)

[Robert M. Muncrief]

Same problem on Ubuntu 14.04.2. Can't install fglrx for HD3300.
version.h is missing. The worst part is that the default drivers are
very slow and trying to run a virtual machine with them is almost
impossible. I hope this can be fixed, it seems it's been a problem for a
long time.

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

Title:
  fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel
  includes at ... not found or incomplete file: .../linux/version.h)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/859101/+subscriptions

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

[Bug 1393060] [NEW] ICU 53.1 or Greater Update for Lao Word and Line Breaking

[Robert M Campbell]

Public bug reported:

Lao line and word break support is needed to properly render Lao text on
various applications, as Lao typically doesn't uses spaces between
words, but rather mostly uses spaces like punctuation, a way to split
phrases.

An example of this is at
http://laosabbathschool.com/development/ssd/site/blog/comprehensive-
zwsp-test/

This text contains no zero-width-spaces, which are commonly used as a
workaround.

If you visit that page with the latest Google Chrome, an iPhone 8.1, or
Android 5.0 device, it'll probably look fine. The the current version of
LibreOffice also handles the text very well, if copied and pasted into a
document, and even includes word counts (may require setting the CTL to
Lao). But with other software (kate for instance), you'll see that the
lines are not equally distributed, and sometimes requires horizontal
scrolling. This creates problems with various applications, such as text
editors, email programs, and anything that renders text on multiple
lines.

Copy and paste the example text to various applications, and you will
see how they handle it. If those applications relied on the system's
version of ICU, an update to ICU 53.1 or greater should take care of
that problem. If they embed their own, then it may or may not work,
depending on what version they included. But at least the update should
help several programs support Lao text.

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

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

Title:
  ICU 53.1 or Greater Update for Lao Word and Line Breaking

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

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

[Bug 1092651] Re: CCSM segfaults if no settings found

[Robert M]

Note: this is still at least partially broken in the newest version of
compiz, as getGnomeMouseButton could still potentially fail(see my
comment #4)

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

Title:
  CCSM segfaults if no settings found

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

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

[Bug 806277] [NEW] Update Package to 2.14.1 in Oneiric

[Robert M Campbell]

Public bug reported:

Is it possible for someone to release the latest stable version of
lilypond(2.14.1) in Ubuntu Oneiric? Currently, the repository contains
an outdated version.

Here is a list of changes to 2.14 since 2.12:
http://lilypond.org/doc/v2.14/Documentation/changes/index.html

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

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

Title:
  Update Package to 2.14.1 in Oneiric

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

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

[Bug 806277] Re: Update Package to 2.14.1 in Oneiric

[Robert M Campbell]

My current Ubuntu version is Natty (11.04) but am willing to use Oneiric
(or backport) if needed. Thanks!

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

Title:
  Update Package to 2.14.1 in Oneiric

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

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

[Bug 806283] [NEW] Lao language renders in pdf poorly

[Robert M Campbell]

Public bug reported:

Lao PDF rendering support for lyrics in Lilypond has issues when
rendering the consonants with long tails. The problem is that Mai Gong
{0EBB} appears as yor {0E8D} after por {0E98}, yor {0EA2}, for {0E9D}
and for {0E9F}. After speaking with a friend, other programs have the
same problem.

Using Ubuntu Natty (11.04) and LilyPond 2.12.3 from the Natty
Repository.

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

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

Title:
  Lao language renders in pdf poorly

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

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

[Bug 312756] Re: MASTER: support graphics card hot switch

[Robert M.]

Hi all,
My laptop is a ASUS K52Jc.
A DSDT.dsl has already been posted for this one, but since mine looked a bit 
different, thought I'd post it too.
Dunno if it helps.

System-product-name  system-product-version
K52Jc
1.0

lspci -vnnn
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor 
Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA 
controller])
01:00.0 VGA compatible controller [0300]: nVidia Corporation GT218 [GeForce 
310M] [10de:0a70] (rev ff) (prog-if ff)

Regards

** Attachment added: alternate DSDT.dsl for ASUS K52Jc
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/312756/+attachment/1852480/+files/DSDT.dsl

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

Title:
  MASTER: support graphics card hot switch

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

[Bug 96311] Re: Feisty Fawn beta doesn't install on Toshiba Tecra S3

[Robert M. Albrecht]

Hi. Fixed in 2.6.26

http://bugzilla.kernel.org/show_bug.cgi?id=9491

cu romal

-- 
Feisty Fawn beta doesn't install on Toshiba Tecra S3
https://bugs.launchpad.net/bugs/96311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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

Re: [Bug 180023] Re: Pidgin crashes when incoming message received (Ubuntu 7.10)

[Robert M. Koch]

Bug disappeared after the reinstall -- sorry I couldn't help track it
down, although from the looks of it, it lives in someone else's
codebase anyway. Thanks for a great IM client!

-- 
Pidgin crashes when incoming message received (Ubuntu 7.10)
https://bugs.launchpad.net/bugs/180023
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

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

Re: [Bug 180023] Re: Pidgin crashes when incoming message received (Ubuntu 7.10)

[Robert M. Koch]

Unable to reproduce; in the interim I had to wipe/reinstall system,
and I can't reproduce the bug now. Methinks it had to do with other
programs installed on the system, maybe vmware or matlab. I'll keep
track of Pidgin's behavior as I install the things I used before, and
I'll grab that trace if/when it reproduces -- and let you know what
the magic package was. Thanks!

On Wed, Feb 13, 2008 at 3:09 PM, Pedro Villavicencio [EMAIL PROTECTED] wrote:
 Thanks for your bug report. Please try to obtain a backtrace
  http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
  bug report. This will greatly help us in tracking down your problem.

  ** Changed in: pidgin (Ubuntu)
Importance: Undecided = Medium
Status: New = Incomplete



  --
  Pidgin crashes when incoming message received (Ubuntu 7.10)
  https://bugs.launchpad.net/bugs/180023
  You received this bug notification because you are a direct subscriber
  of the bug.



-- 
All of the books in the world contain no more information than is
broadcast as video in a single large American city in a single year.
Not all bits have equal value.
  - Carl Sagan

-- 
Pidgin crashes when incoming message received (Ubuntu 7.10)
https://bugs.launchpad.net/bugs/180023
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

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

[Bug 96311] Re: Feisty Fawn beta doesn't install on Toshiba Tecra S3

[Robert M. Albrecht]

Yes.

See http://bugzilla.kernel.org/show_bug.cgi?id=8933

-- 
Feisty Fawn beta doesn't install on Toshiba Tecra S3
https://bugs.launchpad.net/bugs/96311
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] Re: compiz seg-faults on starting

[Robert M. Albrecht]

I used the driver manager to enable to before, so I had to disable the
driver first, reboot and enable the driver again.

This produced a non working xorg.

I had to restore the older xorg manually. The ARGB setting was in there
before and is includes now. Still compiz does not work.



** Attachment added: Xorg.0.log
   http://launchpadlibrarian.net/8293755/Xorg.0.log

-- 
compiz seg-faults on starting
https://bugs.launchpad.net/bugs/122869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] Re: compiz seg-faults on starting

[Robert M. Albrecht]

** Attachment added: messages
   http://launchpadlibrarian.net/8293762/messages

-- 
compiz seg-faults on starting
https://bugs.launchpad.net/bugs/122869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] Re: compiz seg-faults on starting

[Robert M. Albrecht]

** Attachment added: xorg.conf
   http://launchpadlibrarian.net/8293763/xorg.conf

-- 
compiz seg-faults on starting
https://bugs.launchpad.net/bugs/122869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] Re: compiz seg-faults on starting

[Robert M. Albrecht]

** Attachment added: xdpyinfo
   http://launchpadlibrarian.net/8256010/xdpyinfo.log

-- 
compiz seg-faults on starting
https://bugs.launchpad.net/bugs/122869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] Re: compiz seg-faults on starting

[Robert M. Albrecht]

** Attachment added: glxinfo
   http://launchpadlibrarian.net/8256009/glxinfo.log

-- 
compiz seg-faults on starting
https://bugs.launchpad.net/bugs/122869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] Re: compiz seg-faults on starting

[Robert M. Albrecht]

** Attachment added: logfile
   http://launchpadlibrarian.net/8256004/.xsession-errors

-- 
compiz seg-faults on starting
https://bugs.launchpad.net/bugs/122869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] Re: compiz seg-faults on starting

[Robert M. Albrecht]

** Attachment added: xorg-log
   http://launchpadlibrarian.net/8256005/Xorg.0.log

-- 
compiz seg-faults on starting
https://bugs.launchpad.net/bugs/122869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 122869] compiz seg-faults on starting

[Robert M. Albrecht]

Public bug reported:

Binary package hint: compiz

Compiz faults when starting. effects are enabled but the window-
decorations are missing. Happens every time.

I'm using gutsy 2007-06-28 with nvidia-binary driver on a Toshiba Tecra
Laptop.

[EMAIL PROTECTED]:~$ compiz --replace 
[1] 6130
[EMAIL PROTECTED]:~$ Checking for texture_from_pixmap: present. 
Checking for non power of two support: present. 
Checking for Composite extension: present. 

***MEMORY-WARNING***: gconftool-2[6144]: GSlice: g_thread_init() must be called 
before all other GLib functions; memory corruption due to late invocation of 
g_thread_init() has been detected; this program is likely to crash, leak or 
unexpectedly abort soon...
Converting gconf plugin list: ''
***MEMORY-WARNING***: gconftool-2[6146]: GSlice: g_thread_init() must be called 
before all other GLib functions; memory corruption due to late invocation of 
g_thread_init() has been detected; this program is likely to crash, leak or 
unexpectedly abort soon...
Checking for nVidia: present. 
Checking for Xgl: not present. 

***MEMORY-WARNING***: gtk-window-decorator[6151]: GSlice: g_thread_init() must 
be called before all other GLib functions; memory corruption due to late 
invocation of g_thread_init() has been detected; this program is likely to 
crash, leak or unexpectedly abort soon...
Adding plugin imgjpeg (imgjpeg)
Adding plugin annotate (annotate)
Adding plugin scale (scale)
Adding plugin resizeinfo (resizeinfo)
Adding plugin text (text)
Adding plugin resize (resize)
Adding plugin put (put)
Adding plugin glib (glib)
Adding plugin snap (snap)
Adding plugin vpswitch (vpswitch)
Adding plugin opacify (opacify)
Adding plugin rotate (rotate)
Adding plugin move (move)
Adding plugin wall (wall)
Adding plugin png (png)
Adding plugin water (water)
Adding plugin screenshot (screenshot)
Adding plugin regex (regex)
Adding plugin zoom (zoom)
Adding plugin decoration (decoration)
Adding plugin expo (expo)
Adding plugin animation (animation)
Adding plugin ring (ring)
Adding plugin inotify (inotify)
Adding plugin fs (fs)
Adding core settings (General Options)
Adding plugin blur (blur)
Adding plugin neg (neg)
Adding plugin cube (cube)
Adding plugin video (video)
Adding plugin plane (plane)
Adding plugin svg (svg)
Adding plugin minimize (minimize)
Adding plugin switcher (switcher)
Adding plugin fade (fade)
Adding plugin place (place)
Adding plugin winrules (winrules)
Adding plugin clone (clone)
Adding plugin dbus (dbus)
Adding plugin wobbly (wobbly)
Adding plugin scaleaddon (scaleaddon)
Adding plugin thumbnail (thumbnail)

***MEMORY-WARNING***: [6152]: GSlice: g_thread_init() must be called before all 
other GLib functions; memory corruption due to late invocation of 
g_thread_init() has been detected; this program is likely to crash, leak or 
unexpectedly abort soon...
Backend : gconf
Integration : true
Profile : default
Initializing core options...done
Initializing annotate options...done
Initializing resize options...done
Initializing move options...done
Initializing screenshot options...done
Initializing zoom options...done
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
Initializing decoration options...done
Initializing animation options...done
Initializing neg options...done
/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 
image format
Initializing video options...done
Initializing svg options...done
Initializing minimize options...done
Initializing fade options...done
Initializing place options...done
inotify_add_watch: No such file or directory
Initializing snap options...done
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (wall) - Error: Couldn't create cairo context for switcher
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (wall) - Error: Couldn't create cairo context for switcher
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (wall) - Error: Couldn't create cairo context for switcher
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (wall) - Error: Couldn't create cairo context for switcher
Initializing wall options...done
Initializing cube options...done
/usr/bin/compiz.real (cube) - Warn: Failed to load slide: 

Initializing switcher options...done
Initializing scale options...done
Initializing rotate options...done
Initializing expo options...done
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
/usr/bin/compiz.real (core) - Warn: No GLXFBConfig for depth 32
Segmentation fault (core dumped)

***MEMORY-WARNING***: metacity[6130]: GSlice: g_thread_init() must be called 
before all other GLib functions; memory corruption due to late invocation of 
g_thread_init() 

[Bug 107337] gpg does not recognise Omnikey 4040 Smartcard-reader

[Robert M. Albrecht]

Public bug reported:

Binary package hint: casper

gpg does not recognise Omnikey 4040 Smartcard-reader

GPGs homepage lists the 4040 as supported. Ubuntus GPG does not support
this device:

Inserting the smartcard-reader:

[ 1501.256000] pcmcia: registering new device pcmcia0.0
[ 1501.504000] OMNIKEY CardMan 4040 v1.1.0gm5 - All bugs added by Harald Welte
[ 1501.504000] cm4040_cs 0.0: foo

Lauching gpg:

[EMAIL PROTECTED]:~$ gpg --card-edit
gpg: pcsc_connect failed: unknown reader (0x8019)
gpg: card reader not available
gpg: OpenPGP Karte ist nicht vorhanden: Allgemeiner Fehler

Befehl

** Affects: gnupg (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

** Changed in: gnupg (Ubuntu)
Sourcepackagename: casper = gnupg

-- 
gpg does not recognise Omnikey 4040 Smartcard-reader
https://bugs.launchpad.net/bugs/107337
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 96311] Feisty Fawn beta doesn't install on Toshiba Tecra S3

[Robert M. Albrecht]

I confirm this behaviour on my Tecra S3. It was OK with 6.10

I think it is an upstream-problem, as recent Fedora have the same
problems.

romal

-- 
Feisty Fawn beta doesn't install on Toshiba Tecra S3
https://bugs.launchpad.net/bugs/96311
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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

[Bug 96508] Installer does not see harddisk

[Robert M. Albrecht]

Public bug reported:

Hi,

I'm using an Toshiba Tecra S3. Ubuntu 6.10 does install flawless, Feisty
Fawn Beta 2 Installer CDs boots up correctly. I can launch the
installer, choose the language, ... but the partition-tool does not see
any harddisks.

If i do an

rmmod ata_piix
rmmod ahci
insmod ahci.ko

the harddisk appears and the installation goes well. After rebooting the
system dies again, as the harddisk has vanhished

cu romal

** Affects: Ubuntu
 Importance: Undecided
 Status: Unconfirmed

-- 
Installer does not see harddisk
https://launchpad.net/bugs/96508

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

[Bug 96508] Re: Installer does not see harddisk

[Robert M. Albrecht]

*** This bug is a duplicate of bug 96311 ***

** This bug has been marked a duplicate of bug 96311
   Feisty Fawn beta doesn't install on Toshiba Tecra S3

-- 
Installer does not see harddisk
https://launchpad.net/bugs/96508

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