Public bug reported:
Trying to use the openstacksdk to call cinder's migrate_volume and i was
not getting any return code. The cinder API returns a 400 because the
volume I'm trying to migrate has a snapshot, so it will always fail.
The problem is the openstacksdk doesn't return anything from
I've been running 21.10 since it was released and I haven't had the
problem on it. I honestly don't recall if I still had the issue on
21.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905519
It took a very long time before I got a response.but unfortunately
I don't use the computer and system anymore.thanks very much...and kind
regards
Op za 15 jan. 2022 15:15 schreef Paul White
<1703...@bugs.launchpad.net>:
> No response from reporter so closing as 'Invalid'.
>
> **
Public bug reported:
it's happen after a with a fresh install
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: vanilla-gnome-desktop 0.89
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
AptOrdering:
Sorry to add to an old issue, but I can confirm the issue persists under
Ubuntu 18.04.5.
I can reliably reproduce the issue when installing 18.04.5 on physical
hardware, Lenovo ThinkPad P15 (20SUS5LJ00). The error message after
changing the passphrase in gnome-disks is:
Error changing
I'm running Ubuntu 20.10.
But I think I can answer my own question. It just happened again, and
this time all I needed to run was run `apt update`. I didn't even
install anything! A quick google search found this page:
https://www.linuxuprising.com/2020/07/how-to-restart-gnome-shell-from-
This has happened to me twice in the last two days. Until the fix is
available, is there any way to recover from it aside from rebooting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905519
Title:
Fix /etc/default/isc-dhcp-server helps:
Mar 29 17:13:41 mn-wifidhcp02 systemd[1]: Started ISC DHCP IPv4 server.
Mar 29 17:13:41 mn-wifidhcp02 sh[13678]: Internet Systems Consortium DHCP
Server 4.3.5
Mar 29 17:13:41 mn-wifidhcp02 sh[13678]: Copyright 2004-2016 Internet Systems
Consortium.
Mar 29
Opps!
Problem in 4.3.5-3ubuntu7.2 caused by settings in file
/etc/default/isc-dhcp-server
Very strange, because 4.3.5-3ubuntu7.1 working correctly
Check if revert previous behaviour is possible
# cat /etc/default/isc-dhcp-server
# Defaults for isc-dhcp-server (sourced by
Public bug reported:
After updating isc-dhcp-server from 4.3.5-3ubuntu7.1 to 4.3.5-3ubuntu7.2 dhcpd
failed to start
After downgrade dhcpd still working
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.5 LTS
Release:18.04
Codename:
To be clear, comment #13 appears to be a duplicate of the bug report in
comment #14.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915481
Title:
[nvidia] gnome crashes with Fatal IO errors (lost
This appears to be a duplicate of
https://bugs.launchpad.net/bugs/1905519
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915481
Title:
[nvidia] gnome crashes with Fatal IO errors (lost connection
Something different happened tonight, but it feels related so I'm going
to post it with this bug report.
Tonight I did an apt upgrade for a single package -- containerd. Gnome
didn't crash this time, but a short time later I noticed that
/var/log/syslog was filling up with the following messages:
This is the output of journalctl -b0 > journal.txt after a recent crash
of gnome-shell after I ran `sudo apt upgrade`. The problems start at
roughly Mar 03 19:15:58.
** Attachment added: "journal.txt"
I just had gnome crash on me again while running `sudo apt upgrade`.
Only 3 packages were updated. Here's the latest entry in
/var/log/apt/history.log:
Start-Date: 2021-03-03 19:16:46
Commandline: apt upgrade
Requested-By: waltman (1000)
Upgrade: python3-twisted:amd64 (18.9.0-11,
I believe the crash happened at roughly Feb 11 19:42:41.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915481
Title:
gnome crashes after running `apt upgrade`
To manage notifications about this
Reproducing the crash exactly is basically impossible -- I have no idea
what I was doing to trigger it on January 6. The crashes I've been
experiencing happen seemingly at random while running `apt update`. It
may well happen again in the future, but based on past experiences it
will be with a
Out from running
journalctl -b-1 > prevjournal.txt
** Attachment added: "prevjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+attachment/5463784/+files/prevjournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for replying so quickly. Unfortunately step 1 didn't show any
crash reports.
Step 2 doesn't show anything recent, but there were crashes on January 6
that might be relevant. They are:
gnome-control-center:
https://errors.ubuntu.com/oops/28c05820-501b-11eb-9503-fa163e983629
gnome-shell:
On second thought, a better title would be "gnome crashes WHILE running
apt upgrade" because it always happens while it's in the middle of
installing the new packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is the second time this week this has happened, and perhaps the
tenth time in the past few months. This time the packages it was
updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1),
libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1),
stable release update in Ubuntu 20.04 requires very good
> grounds: https://wiki.ubuntu.com/StableReleaseUpdates
>
> If 2.0.5 is urgently needed in Ubuntu 20.04, please help us document the
> motivations for it here.
Totally understandable.
Walt
--
You received this bug notificati
My apologies. I resolved this locally back in April but I forgot to come
back here and update the ticket when I resolved the problem. This is a
known bug that has been fixed in the rdiff-backup repo:
https://github.com/rdiff-backup/rdiff-backup/issues/310
The code was fixed way back in March,
I just hit this problem while trying to do a do-release-upgrade from
ubuntu 18.04 to 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows:
Public bug reported:
The focal package for python3-pastescript is based on a python2 only
package that was released in 2015 and doesn't work in focal.
https://packages.ubuntu.com/focal/python3-pastescript
Here is the upstream package history
https://pypi.org/project/PasteScript/2.0.2/#history
I modified get_indexpath() in log.py to catch a TypeError exception and
return the string "TypeError" instead of aborting. It printed 4 errors:
ListError: 'TypeError' [Errno 13] Permission denied: b'/run/user/1000/doc'
ListError: 'TypeError' [Errno 13] Permission denied: b'/run/user/1000/gvfs'
I'm afraid I don't know nearly enough Docker to be able to do that. But
I do know Python. I just took a look at the code and I think I should be
able to trap the TypeError exception pretty easily.
I'm currently running `rdiff-backup --check-destination-dir` to undo the
failed backup. Once that
Public bug reported:
Here's the output from last night's cronjob:
Subject: Cron if [ -x /backup/scruffy ]; then rdiff-backup
--print-statistics --exclude-filelist /usr/local/etc/rdiff_exclude /
/backup/scruffy; fi
I also had this problem. After running the command suggested above:
snap connect chromium:password-manager-service
it's now working again for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In 19.04 supertuxkart stores its configuration in
~/.config/supertuxkart/0.8.2/. In 19.10 it's stored in config-0.10/. The
old configuration doesn't seem to be used at all when starting the game
for the first time.
I asked on the #supertuxkart channel on freenode. They
Public bug reported:
ufw package contains /etc/rsyslog.d/20-ufw.conf, but no
/etc/syslog-ng/conf.d/ufw.conf
distro: any
ufw: any
** Affects: ufw (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
"So Digium TE13x cards do not work unless the following lines are added
to dkms.conf & drivers are rebuilt -"
It's been over a year and this issue still exists. I would be very happy
if someone could provide more guidance/instructions on how to do the
"drivers are rebuilt" portion of this so that
Thank you everything okay now .. kind regards
2018-02-06 21:04 GMT+01:00 Christopher M. Penalver <
christopher.m.penal...@gmail.com>:
> walt, thank you for reporting this and helping make Ubuntu better.
>
> To advise, your logs indicate that the wireless hardware isn't
> inst
Public bug reported:
wifi
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CompizPlugins: No value set for
Public bug reported:
When new applications are launched from the terminal in 17.10, the
windows are unfocused and appear below the current window. This is the
opposite of the behavior in (at least) 16.10 and 17.04, where new
windows would appear focused and on top. This appears to be a feature in
Public bug reported:
Several programs in this package, notably xload and xcalc, don't have
icons in the new dock in 17.10. Most of the others (e.g. xclock, xeyes)
do.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: x11-apps 7.7+6ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic
Public bug reported:
it was automatic
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-83.106-lowlatency 4.4.70
Uname: Linux 4.4.0-83-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set
I'm also seeing this. After you configure the wlan0 settings and then
hit done to apply the configuration, the wlan0 interface vanishes and
never comes back w/o a reboot as well. The progress stops at 66% and
never resumes.
--
You received this bug notification because you are a member of
Public bug reported:
Ubuntu 17.04 ships with netbase 5.4, which removes a number of protocols
from /etc/services. One of these is imap3 (220/tcp) which is used by
several entries in /etc/fail2ban/jail.conf. This led to the following
messages in /var/log/fail2ban.log:
iptables -w -I INPUT -p tcp
Public bug reported:
I upgraded to 17.04 tonight, and when the install finished I started
getting reports that apcupsd could no longer communicate with my UPS.
The problem turned out to be that /etc/apcupsd/apcupsd.conf was silently
overwritten by the installer. It changed the UPSCABLE and
Public bug reported:
The postfix jails in fail2ban look in the mail.warn log. But the default
install of rsyslog has the mail.warn rule commented out, so nothing gets
logged there. Also I think the messages it's looking for go to mail.log,
not mail.warn.
** Affects: fail2ban (Ubuntu)
I figured out what my problem was, and since I haven't seen any
solutions anywhere else, hopefully this will be of some use to the next
person. In my case it turned out to be the Nvidia driver, which
installed its modules under /lib/modules/4.8.0-32-generic. When I
upgraded to 4.8.0-34, it
Sorry, that should be 4.8.0-34 and 4.8.0-32.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511824
Title:
Can't login as ordinary user with lightdm
To manage notifications about this bug go to:
I'm seeing the same thing in 16.10, with kernel 4.0.8-34 that just hit
yesterday. When I boot from the previous kernel (4.0.8-32) I can still
login.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I experienced this bug without changing the default keyboard layout, so
I don't think it is Neo2.
W.r.t. power supply: I typically experience it *more* frequently on
battery power, but it happens with both.
My current workaround is... using an external keyboard.
--
You received this bug
This is exactly the behavior I see on my machine.
Linux shinobi 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
66CN55WW
02/28/2013
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hooray Hooray.. problem # is 1607070. I hope that helps Sebastien.
The file did not allow read access, which caused the submit to fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606358
Title:
the file access was no read
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607070
Title:
additional crash file for 1606358
To manage notifications about this bug go to:
Public bug reported:
attempting to provide the crash file for 1606358
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.14
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
There is this guy..
http://askubuntu.com/questions/802468/menu-bar-and-launcher-missing-after-installing-updates-16-04-lts
which addresses virtualbox specifically.
It wouldn't submit, literally nothing happened. Now that was under a
16.04 image that was upgraded to 16.04.1.
When I did a fresh
This may actually be the same resolution as 1606358. I did see one
launcher icon 'vibrate' so, yes, the launcher is actually off screen.
Also,
http://askubuntu.com/questions/802767/16-04-1-upgraded-vm-cannot-access-
unity-bar-on-left-nor-move-desktop-windows
references this same problem. Does
Sorry, I can NOT get it to submit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606358
Title:
Ubuntu 16.04.1 unity disappears when set to autohide
To manage notifications about this bug go to:
OK, I did describe two steps to reproduce. In the original case, it was
an existing 16.01 current with maintenance, that I in-place upgraded. As
it was existing I had already switched the launcher from autohide=off to
autohide=yes as well I already had a desktop icon. so there were two
artefacts
I guess I don't understand your question concerning what I changed. My
change was to upgrade a perfectly good 16.04 image that functioned
perfectly and after the upgrade and subsequent reboot there was no
louncher and if I started Netbeans 8.1 (a desktop icon) or started a
terminal session, both
Public bug reported:
Initially I was going to report this against a completely working 16.04
VM using spice. In that case the system, once rebooted after the upgrade
failed to show launcher at all and no desktop applications could be
moved. This is new behavior in 16.04.1. All these things worked
$ snap --version
snap
snapd unknown (series 16)
This is on Ubuntu 16.04
root ~ cat /etc/issue
Ubuntu 16.04 LTS \n \l
root ~ uname -a
Linux waboring-HP-Z620-Workstation 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18
18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
--
You received
Public bug reported:
cat /etc/issue
Ubuntu 16.04 LTS \n \l
snap login
Password:
error: cannot get package access macaroon from store: Post
https://myapps.developer.ubuntu.com/api/2.0/acl/package_access/: x509:
certificate is valid for FG3K6C3A13800676, not myapps.developer.ubuntu.com
**
I see the same on my Yoga. When this happened a few years ago, the fix
was to update the BIOS (now 66CN55WW). A recent kernel upgrade broke
this again (I saw the problem return after upgrading to 16.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can no longer get a desktop login into my system. What can be done to
circumvent 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/1485277
Title:
unity-settings / compiz segfault and ui
We would like to have these additional patches picked up for the first
SRU for the 15.04 release. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452200
Title:
suggested patches for lpfc
Bug 1439612 was meant to identify our solution for the 14.04.03 release.
We were unable to get all the patches/fixes we wanted for this driver,
as a number of fixes were not yet accepted into the kernel maintainer's
tree.
We were informed that 14.04.03 was locked down.
So, we opened this bug to
Hi Brian, we are using this bug to track our submission for 14.04 (3.13
kernel). we are using bug 1439612 to track our submission for 14.04.03
(3.19 kernel) submission.
Nikhith's request would be to set the version number for the driver in
14.04 update.
Thanks,
Walt
--
You received this bug
probably ask the team to pull in a few more patches for
consideration for this driver candidate for your Vivid kernel release.
Thanks,
Walt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1439612
Title
and communicate our progress
on getting the Upstream patch pushed to the scsi misc list and then we
can track the progress together.
Walt
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Brian
Fromme
Sent: Wednesday, April 01, 2015 4:29 PM
To: Walt Esker
https://bugs.launchpad.net/ubuntu/+source/mplayer2/+bug/1426720
That's the new bug. It'll get marked as a duplicate and this one will
hopefully get reopened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This absolutely has NOT beed fixed. I'm filing a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363877
Title:
mencoder package not available in 14.10
To manage notifications about this
Public bug reported:
The previous bug #1363877 was marked fixed released when the problems
has NOT been fixed.
mencoder is still not available. it doesn't get installed with
mplayer2.
** Affects: mplayer2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
This problem appeared immediately after running software update on
2015-02-26 UTC-700. The Xubuntu login screen fails to appear after
boot. It is possible to log in on the console at Ctrl-Alt-F2. Before
running update and rebooting, the login screen appeared normally.
I just tried to update and reinstall mplayer2 and it doesn't have
mencoder
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363877
Title:
mencoder package not available in 14.10
To manage
** Changed in: cinder
Assignee: Walt Boring (walter-boring) = Richard Hagarty (richard-hagarty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331945
Title:
Zones are getting created for all
** Changed in: cinder
Milestone: None = kilo-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331945
Title:
Zones are getting created for all the available ports in Host- BRCD
Zone Manager
wallch doesn't work behind an http proxy. It doesn't honor the
http_proxy, https_proxy shell environment variables.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031654
Title:
Unable to connect
Public bug reported:
This was part of an autoupdate and it failed on Aprinl 23 2014.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mysql-server-5.5 5.5.37-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
Uname: Linux 3.2.0-60-generic x86_64
Public bug reported:
This was part of an autoupdate and it failed on Aprinl 23 2014.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mysql-server-5.5 5.5.37-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
Uname: Linux 3.2.0-60-generic x86_64
(Sorry, that's 66CN51WW to 66CN55WW)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291258
Title:
[Lenovo IdeaPad Yoga 13] Stuck keys
To manage notifications about this bug go to:
I can confirm that moving from 66CN55W1 to 66CN55WW (02/28/2013) fixes
the problem.
Christopher, thank you so much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291258
Title:
[Lenovo IdeaPad
Public bug reported:
On the Lenovo Yoga 13 some keys, when being held down, are not released
(e.g. pagedn, up arrow, etc.). Once this happens, the mouse cursor also
starts scrolling in some or other direction (it can be moved with the
track-pad, but keeps moving in that direction).
Using an
Thanks, done:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1291258
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238914
Title:
Random stuck keys on Lenovo Yoga 13
To manage notifications
I can confirm this bug on my Lenovo Yoga 13 running 3.11.0-17-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238914
Title:
Random stuck keys on Lenovo Yoga 13
To manage notifications
This bug is happening against stable/grizzly now as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1185178
Title:
glanceclient tests failing on fake_host
To manage
** Tags added: grizzly-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1185178
Title:
glanceclient tests failing on fake_host
To manage notifications about this
This bug is happening against stable/grizzly now as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185178
Title:
glanceclient tests failing on fake_host
To manage notifications about this
** Tags added: grizzly-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1185178
Title:
glanceclient tests failing on fake_host
To manage notifications about this bug go to:
Public bug reported:
Firefox 23 on Ubuntu 13.10 with gnome-shell Xfce installed. I can
download and select themes other than default. Firefox restarts behaves
correctly. However, on the next restart or on the second restart, the
default theme is active even though I do not wish it. I've
I had this problem with 12.04 on my laptop. After accepting an upgrade I
could no longer boot back in. I agree that acpi=off works solidly but,
from everything I've read, bad stuff can result. One thing I've noticed
myself as well as listening to others is you need to reboot several
times to be
For future googlers: dconf-editor is an easier way to set the (very
stupid) gnome middle-button setting.
Run dconf-editor from a command prompt and navigate to org::gnome
::settings-daemon::mouse. You should see the middle-button-enabled
checkbox in the right-hand panel.
You should find this
install, even for desktop. I believe in the 8. or certainly
the 9. time frame it would with the standard install, until 11.10 where
it once again broke.
Walt
On 04/11/2012 10:49 AM, Steve Langasek wrote:
Can anyone reproduce the originally reported issue with the 12.04 beta?
The developers have
Private bug reported:
Crash occurred after printing a single graphics page to a Brother MFC-
J430W. Graphics pages seem slow to spool to printer, print speed is
normal. This behavior occurrs in 12.04 only.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: brother-cups-wrapper-common
This appears to be alive well in 12.04 so far as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761824
Title:
indicator-weather crashed with SIGSEGV in g_type_check_instance_cast()
To manage
This bug is pretty old but the error is the same. The crash occurred in
Ubuntu x86_64 while trying to burn an .iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120927
Title:
[apport] brasero
Crash occurred with 12.04 current as of 12 Feb. 2012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/827655
Title:
indicator-weather crashed with SIGSEGV in g_array_free()
To manage notifications
Public bug reported:
crash occurred while installing Precise Pangolin from a USB drive
created with Unetbootin
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.11
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
Uname: Linux 3.2.0-11-generic x86_64
ApportVersion:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922845
Title:
installer crashed while installing 12.04 amd64 daily
To manage notifications about this bug go to:
Public bug reported:
I had an existing 10.10 install on this very machine with firmware raid
0. I installed 4 500GB drives as raid 5 and the install worked right up
until the end when it failed.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubiquity 2.8.7
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896658
Title:
unable to write bootloader on frosh install of 11.10 on firmware raid
5
To manage notifications about this bug go to:
Hi Petr,
Thank you. I will try it - next time I install Ubuntu with Unity.
Greetings,
Fanie van der Walt.
On 24/10/2011 11:40, Petr Hlozek wrote:
Hi Bilal,
I had the same problem in my Lazarus application. Finally, I solved it.
You have to set LIBOVERLAY_SCROLLBAR to 0 directly in your
Bug still exists for zoneminder 1.24.2-2build3 on Ubuntu 10.04.2 LTS.
Above fix will allow for exporting of events from the event listing
window but not from the event details window. This also breaks video
generation from the event details window.
--
You received this bug notification because
Public bug reported:
One of the main features is the ability to export captured events from
ZoneMinder. The export window allows two compression formats, tar and
zip. Most Windows users will choose Zip but the zoneminder package
dependencies don't include the zip package and binaries.
**
Stephane - In my case the level was Natty and the target was a Dell
system with firmware RAID 1 against two 750 GB drives. It never wrote
grub out. I could not get install to install grub. I ended up having to
disable firmware RAID and fumbling through software RAID. Ubuntu has
supported firmware
** Changed in: unity (Ubuntu)
Assignee: (unassigned) = Nico van der Walt (nicovdw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736162
Title:
Control keys display as graphic chars
1 - 100 of 205 matches
Mail list logo
