Workaround: 'readelf -n core' and look at the first mapped file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511720
Title:
fails to identify what program left a core file
To manage
I attached the unity logs from .cache/upstart.
I also noticed something weird, if i log into xfce then log back out and
choose unity it starts xfce, this only happens if i have logged in to
xfce and back out.
** Attachment added: "unity-cache_upstart.log"
I found the problem, on do-release-upgrade it removed (I don't know why,
but it's my fault to not notice that):
screen-resolution-extra:amd64 (0.17.1, automatic), libjansson4:amd64
(2.7-1ubuntu1, automatic), nvidia-settings:amd64
(358.09-0ubuntu0~gpu15.10.1, automatic), libcuda1-355:amd64
Public bug reported:
Running Ubuntu Xenial Xerus.
Unity won't start.
What happens is, when I try to login it just throws me back to the login screen
after a few seconds.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic
Btw, it did boot into fxce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511567
Title:
Unity won't start
To manage notifications about this bug go to:
** Package changed: xorg (Ubuntu) => unity (Ubuntu)
** Summary changed:
- Unity won't start
+ Unity won't start on login
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511566
Title:
Unity won't
Public bug reported:
Running Ubuntu Xenial Xerus.
Unity won't start.
What happens is, when I try to login it just throws me back to the login screen
after a few seconds.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic
Same issue with 4.2.5-040205-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400235
Title:
10de:11fc [Dell Precision M4800] Screen does not wake up after sleep
To manage notifications
Public bug reported:
$ gnome-calendar
(gnome-calendar:22473): Gtk-CRITICAL **: Error building template class
'GcalWindow' for an instance of type 'GcalWindow': .:155:1 Can't use
Looks like this crash only happens if you've got the gnome3-staging PPA
enabled:
mgedmin, it works in clean wily install
Or, actually, only if you mix gnome-calendar 3.16 with GNOME 3.18
libraries:
mgedmin, crashed here on xenial
but this will be fixed on xenial Soon(TM):
3.18 should sync
*** This bug is a duplicate of bug 1502173 ***
https://bugs.launchpad.net/bugs/1502173
** This bug has been marked a duplicate of bug 1502173
Python warnings: modules imported without specifying a version first
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Importing the keyring module produces a warning:
$ python
Python 2.7.8 (default, Oct 20 2014, 15:05:19)
[GCC 4.9.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import keyring
** Tags added: erm wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268151
Title:
[Dell M4800] DPMS support broken, fails to wake up the monitor after
putting it to sleep
To manage
This bug disappeared some time in Vivid (but the not able to adjust
screen brightness), but now that I upgraded to Wily (15.10), the problem
is back.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Tags added: wily
** Tags removed: latest-bios-a11
** Tags added:
Steps to reproduce:
- in one terminal run /usr/bin/gnome-documents --gapplication-service
- in another terminal run dbus-send --print-reply --dest=org.gnome.Documents
/org/gnome/Documents/SearchProvider
org.gnome.Shell.SearchProvider2.GetInitialResultSet array:string:"search"
Note: you must
** Also affects: tracker (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/1418771
Title:
gjs-console assert failure: *** Error in
I ran the reproduction scenarion under valgrind and saw this:
==23172== Thread 8 pool:
==23172== Invalid write of size 1
==23172==at 0x174A56C1: tracker_parser_unaccent_nfkd_string (in
/usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-common.so.0.0.0)
==23172==by 0x1726AA02:
Experiments show that
Acquire::http::ProxyAutoDetect "/bin/sh -c 'true'";
produces this error:
Failed to exec method /bin/sh -c 'true'
so I'm afraid options 1 and 2 are out :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Experiments show that
Acquire::http::ProxyAutoDetect "/bin/sh -c 'true'";
produces this error:
Failed to exec method /bin/sh -c 'true'
so I'm afraid options 1 and 2 are out :(
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I've some half-formed ideas:
- if apt allows a shell command instead of just an executable name,
maybe the config could be
Acquire::http::ProxyAutoDetect "if [ -x /usr/share/squid-deb-proxy-
client/apt-avahi-discover ]; then /usr/share/squid-deb-proxy-client/apt-
avahi-discover; fi";
- if
I've some half-formed ideas:
- if apt allows a shell command instead of just an executable name,
maybe the config could be
Acquire::http::ProxyAutoDetect "if [ -x /usr/share/squid-deb-proxy-
client/apt-avahi-discover ]; then /usr/share/squid-deb-proxy-client/apt-
avahi-discover; fi";
- if
When Debian packages ship cron files, these usually test -x
/usr/bin/programname before executing it, to prevent errors in case the
package is removed but not purged. I thought it was required by the
Debian policy, but I cannot find wording for it. Maybe it was just a
courtesy.
--
You received
When Debian packages ship cron files, these usually test -x
/usr/bin/programname before executing it, to prevent errors in case the
package is removed but not purged. I thought it was required by the
Debian policy, but I cannot find wording for it. Maybe it was just a
courtesy.
--
You received
Unfortunately this is not fixed.
$ apt-cache policy squid-deb-proxy
squid-deb-proxy:
Installed: 0.8.10
Unfortunately this is not fixed.
$ apt-cache policy squid-deb-proxy
squid-deb-proxy:
Installed: 0.8.10
** Changed in: qt
Status: New => Fix Committed
** Changed in: kcalc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503170
Title:
Numeric keypad not
Same output if I do
sudo apt-get install squid-deb-proxy-client
apport-collect 1501217
I may have filed it against the wrong package? But
apt-cache show squid-deb-proxy-client|grep Source
Source: squid-deb-proxy
so huh? bug in apport?
I'm using Ubuntu 14.04 LTS.
** Changed
apport-collect says
Package squid-deb-proxy not installed and no hook available,
ignoring
*** Updating problem report
No additional information collected.
because of course.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
apport-collect says
Package squid-deb-proxy not installed and no hook available,
ignoring
*** Updating problem report
No additional information collected.
because of course.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same output if I do
sudo apt-get install squid-deb-proxy-client
apport-collect 1501217
I may have filed it against the wrong package? But
apt-cache show squid-deb-proxy-client|grep Source
Source: squid-deb-proxy
so huh? bug in apport?
I'm using Ubuntu 14.04 LTS.
** Changed
** Bug watch added: KDE Bug Tracking System #353596
https://bugs.kde.org/show_bug.cgi?id=353596
** Also affects: kdeutils via
https://bugs.kde.org/show_bug.cgi?id=353596
Importance: Unknown
Status: Unknown
** Changed in: kcalc (Ubuntu)
Status: Invalid => Confirmed
--
You
** Also affects: khotkeys (Ubuntu)
Importance: Undecided
Status: New
** Changed in: kcalc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/580137
Public bug reported:
The numbers in the numeric keypad is not working anymore in this
version. The other number keys are working fine.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: kcalc 4:15.08.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux
** Bug watch added: KDE Bug Tracking System #344638
https://bugs.kde.org/show_bug.cgi?id=344638
** Also affects: kdeutils via
https://bugs.kde.org/show_bug.cgi?id=344638
Importance: Unknown
Status: Unknown
** Also affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
** Also affects: kde-baseapps via
https://bugs.kde.org/show_bug.cgi?id=353596
Importance: Unknown
Status: Unknown
** No longer affects: kdeutils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I updated yesterday and got this issue afterwards.
I tried the following workaround with worked for me :
--- serialposix.py.stock2015-10-03 06:53:45.241261071 -0700
+++ serialposix.py 2015-10-03 06:55:07.481262475 -0700
@@ -457,7 +457,11 @@
# Disconnected devices, at least on
Public bug reported:
If I apt-get remove squid-deb-proxy-client, every apt-get
install/update/upgrade operation produces this error message:
0% [Working]Failed to exec method /usr/share/squid-deb-proxy-client
/apt-avahi-discover
The workaround is to apt-get purge squid-deb-proxy-client.
**
Public bug reported:
If I apt-get remove squid-deb-proxy-client, every apt-get
install/update/upgrade operation produces this error message:
0% [Working]Failed to exec method /usr/share/squid-deb-proxy-client
/apt-avahi-discover
The workaround is to apt-get purge squid-deb-proxy-client.
**
Public bug reported:
N/A
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: foomatic-db-compressed-ppds 20150819-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
Uname: Linux 4.2.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19-0ubuntu1
AptdaemonVersion:
I think this output parsing bug bit me again today:
SegvAnalysis: Skipped: missing required field "Disassembly"
SourcePackage: gdm
Stacktrace:
=> 0x417010: mov0x8(%r15),%rcx
0x417014: test %rcx,%rcx
0x417017: je 0x41709f
0x41701d: mov(%rcx),%rbx
0x417020:
I glanced at the patch and I noticed this line:
> ++territory "Democratic Republic of congo"
Shouldn't "congo" be capitalized?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491880
Title:
Add
Public bug reported:
Lithuania switched currency to the Euro on 1st Jan 2015. The lt_LT
locale ought to be updated accordingly.
** Affects: langpack-locales (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The upstream bug about lv_LV switching to the Euro is interesting:
https://sourceware.org/bugzilla/show_bug.cgi?id=16374.
The situation with lt_LT is very similar, only we got the Euro one year
later. Same legacy 8-bit charset (ISO-8859-13 has no Euro), but
everyone uses UTF-8 now, right?
Filed https://sourceware.org/bugzilla/show_bug.cgi?id=18953
** Bug watch added: Sourceware.org Bugzilla #18953
http://sourceware.org/bugzilla/show_bug.cgi?id=18953
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
upgrading to the -proposed version worked for met too.
$ apt-cache policy wine
wine:
Installed: 1:1.6.2-0ubuntu8.1
Candidate: 1:1.6.2-0ubuntu8.1
Version table:
*** 1:1.6.2-0ubuntu8.1 0
400 http://za.archive.ubuntu.com/ubuntu/ vivid-proposed/universe amd64
Packages
100
Public bug reported:
I had sound before I upgraded from 15.04 to 15.10.
It detects that the headphones are plugged in, but no sound at all.
Speaker works.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
** This bug is no longer a duplicate of bug 117
The default configuration is missing the
/etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in
** This bug is no longer a duplicate of bug 117
The default configuration is missing the
/etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still for the French language, when activating automated punctuation,
the spaces right before the signs ! ? : ; are automatically deleted.
They should be kept in French, like in these examples:
How are you? = Ca va ?
Great! = Super !
This one: = Celui-ci :
first; second = first ; second
** This bug has been marked a duplicate of bug 117
The default configuration is missing the
/etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** This bug has been marked a duplicate of bug 117
The default configuration is missing the
/etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl file
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in
my system is running since i reinstalled some parts that i found in
synaptic after receiving an error message.
so now you can stop sending me the email messages about those bugs.
Thanks for helping me
Marius en Lia van Harten
Bergstrasse 17
49774 Vinnen
Duitsland
Tel.: 0049 (0)5432 9058786
I ran the following commands from the phone's terminal
sudo mount -o remount,rw /
sudo apt-get update
sudo apt-get upgrade
I had an error for the powerd package, it wouldn't install.
Yesterday I reset the phone using the recovery boot and I'm having the
same problem.
--
You received this bug
I know that now. I reset the phone using the factory settings option
in About your phone.
I just finished flashing the phone using BQ's flash utility and
everything's back to normal. I'll close the bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
I received this error when I tried to install kubuntu-desktop from the
kubuntu-ppa channel.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: account-plugin-google (not installed)
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux
Yes, I can run adb shell.
Attached the two .crash files I found in /var/crash/
** Attachment added: crash.zip
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1487839/+attachment/4451851/+files/crash.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Steps to reproduce :
- open a window in Ubuntu Touch
- close it by sliding it up from the list of applications opened
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487839
Title:
Crash when
Public bug reported:
Every time I close a window by sliding it up, Ubuntu Touch crashes and
restarts.
Device : BQ Aquaris E5 HD
OS : Ubuntu 15.04 - armhf (20150713-202300)
** Affects: mir (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
You are totaly right.
My system is running again but I am not sure what happens wenn the new
updat (upgrade) is comming.
So far so good I can use my PC and I say thanks to all off them who
helped me and the other ones.
Marius
Op 21-08-15 om 17:11 schreef QIII:
The thanks are to the individuals
after a long way off struggle my system is running again thanks to all
giving tips and solutions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479913
Title:
SRU request: fglrx.ko fails because of
: dinsdag 18 augustus 2015 14:45
Aan: Marius van Harten
Is this similar to the bug:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1444735
fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build [FATAL:
modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol
Public bug reported:
in todays update
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic i686
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
ApportVersion:
I normaly log-in wthout username and password but now the screen is
everytime comming back to ask my log-in code how can I manage this?
Verzonden met Windows Mail
Van: Nicolas Delvaux
Verzonden: dinsdag 18 augustus 2015 16:11
Aan: Marius van Harten
Well, the new FGLRX is only
As per comment #4, the installation of the package bcmwl-kernel-source
solves the problem and it seems to carry the very same version of the
driver, thus no need for broadcom-sta.
My question is why broadcom-sta (still) exists (at all) in the first
place?
Also when I do apt-cache search BCM4352
Public bug reported:
This bug happened directly after starting the laptop and logging in.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libqt4-opengl:amd64 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1
ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11
Uname: Linux
It's already in 15.10 proposed: https://code.launchpad.net/~ubuntu-
branches/ubuntu/wily/scala/wily-proposed
** Changed in: scala (Ubuntu)
Status: Triaged = Fix Committed
** Branch linked: lp:ubuntu/wily-proposed/scala
** Summary changed:
- Scala 2.10.0 needs packaging
+ Scala 2.11.6
I have the same issue as #14
I still have Black screen with cursor issue, I have tried to
redownload and rebuild, i have also tried --update-lxc, but i can't get
it to work.
I use the ppa
(http://ppa.launchpad.net/unity8-desktop-session-team/unity8-preview-lxc/ubuntu).
I'm running vivid on a
Public bug reported:
I'm running
ubuntu-vm-builder kvm trusty \
--libvirt qemu:///system \
--tmpfs=2048 \
--rootsize 20480 \
--ssh-key=/root/.ssh/authorized_keys
Public bug reported:
I'm running
ubuntu-vm-builder kvm trusty \
--libvirt qemu:///system \
--tmpfs=2048 \
--rootsize 20480 \
--ssh-key=/root/.ssh/authorized_keys
2015-05-22 21:19 GMT+02:00 mohican 1...@bugs.launchpad.net:
***Ubuntu need to be sold pre-installed on 100% compatible harware.***
But this is not enough, people will not buy PCs with an alternative OS on
it. People buy PCs with Windows because they know it and expect it to work
100% (or
Public bug reported:
$ sudo /usr/lib/cyrus/bin/upgrade-db
/usr/lib/cyrus/bin/upgrade-db: 56: /usr/lib/cyrus/bin/upgrade-db:
/usr/sbin/cvt_cyrusdb: not found
$ locate cvt_cyrusdb
/usr/lib/cyrus/bin/cvt_cyrusdb
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cyrus-common
I've already upgraded to vivid so won't be able to do the verification.
** Changed in: xserver-xorg-video-intel (Ubuntu Utopic)
Assignee: Marius Gedminas (mgedmin) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
The init script is looking for /var/run/cyrmaster.pid, which doesn't
exist. The actual pid file is /var/run/cyrus-master.pid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454693
Title:
'service
There was a similar upstream bug about PIDFILE mismatch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778781
Curiously it was just the reverse in Debian: the init script was looking
for /var/run/cyrus-master.pid, but the software actually used /var/run
/cyrus-master.pid.
** Bug watch added:
sudo service cyrus-imapd stop at least says it didn't work
$ pgrep -u cyrus
11769
11804
$ sudo service cyrus-imapd restart
* Restarting Cyrus IMAPd cyrmaster
...fail!
$ pgrep -u cyrus
11769
11804
** Tags added: apport-collected trusty
** Description changed:
$ pgrep -u cyrus
11769
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1454693/+attachment/4396800/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454693
Public bug reported:
$ pgrep -u cyrus
11769
11804
$ sudo service cyrus-imapd stop
$ pgrep -u cyrus
11769
11804
---
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
DistroRelease: Ubuntu 14.04
Package: cyrus-imapd-2.4 2.4.17+caldav~beta9-3
PackageArchitecture: amd64
ProcVersionSignature:
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1454693/+attachment/4396799/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1454693
The command to list Python scripts that have been autoloaded is:
(gdb) info auto-load python-scripts
I'm guessing
/usr/share/gdb/auto-load/lib/x86_64-linux-gnu/libglib-2.0.so.0.4400.0-gdb.py is
the one that causes my problem.
It's a small script that adds /usr/share/glib-2.0/gdb to
gdb in Ubuntu links against libpython3.4.
The Python scripts in /usr/share/glib-2.0/gdb haven't been fully ported
to Python 3: the custom iterators should define a '__next__' method
alias pointing to 'next'.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
**
Somewhat-related upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=720635
** Bug watch added: GNOME Bug Tracker #720635
https://bugzilla.gnome.org/show_bug.cgi?id=720635
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You can see the Disassembly: field contains
$2 = -99Python Exception class 'TypeError' iter() returned non-
iterator of type '_iterator':
which is missing a newline. This breaks apport's output splitting
logic.
The TypeError shows up because of bug 1449389. I think it gets printed
into
A simple fix would be to modify apport.report.Report.add_gdb_info() to
use
_command_output(..., stderr=subprocess.PIPE )
if we don't mind ignoring gdb's stderr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I got a better fix in the linked Bazaar branch. I'm not sure
how to test it: I have the crash file with the base64-encoded core and
incorrectly-decoded fields, how can I convince apport (in a bzr
checkout) re-interpret it?
** Branch linked: lp:~mgedmin/apport/fix-lp1453011
--
You
No, it did not change anything:
$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
A13
01/29/2015
But thanks for pointing out my outdated BIOS. It might solve other
issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Apport sometimes gets confused when analyzing a core dump:
SegvAnalysis: Failure: invalid literal for int() with base 16: '='
I'm attaching the crash file (sans base64-encoded core dump) that
contains this and some other wonderful examples, like
Registers: $6 = 0x0
** Attachment added: the strange apport crash file
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1453011/+attachment/4393424/+files/gnome-shell.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream bug with a patch:
https://bugzilla.gnome.org/show_bug.cgi?id=749092
** Bug watch added: GNOME Bug Tracker #749092
https://bugzilla.gnome.org/show_bug.cgi?id=749092
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, I installed version 349.16 using xorg-edgers, but it did not change
anything. I guess this is an regression issue with the kernel instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452173
Public bug reported:
In Ubuntu 15.04, I no longer am able to control the screen brightness.
See possible similar bug #1411514 for 14.04.1.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux
Upstream bug: https://github.com/mitchellh/vagrant/issues/4618
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452148
Title:
vagrant box outdated thinks the box is outdated; vagrant box update
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411514
Title:
[Dell Precision M4800] Brightness can't be controlled on 14.04.1
To manage notifications about this bug go to:
Public bug reported:
$ vagrant box outdated --global
* 'ubuntu/trusty64' is outdated! Current: 20150422.0.1. Latest: 20150427.0.0
$ vagrant box update --box ubuntu/trusty64
Checking for updates to 'ubuntu/trusty64'
Latest installed version: 20150427.0.0
Version constraints: 20150427.0.0
For the record this affects 14.04 LTS too.
** Summary changed:
- Postgrey does not stop
+ Postgrey does not stop after 'sudo service postgrey stop'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As a workaround I replaced /etc/init.d/postgrey with
http://sources.debian.net/src/postgrey/1.35-1/debian/postgrey.init/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981789
Title:
Postgrey does
Public bug reported:
I tried to gdb a gnome-shell segfault:
(gdb) bt
#0 0x7f8cad51f638 in g_slice_alloc (magazine_chunks=0xf879b0) at
/build/buildd/glib2.0-2.44.0/./glib/gslice.c:535
#1 0x7f8cad51f638 in g_slice_alloc (tmem=optimized out, ix=1) at
Can this bug please be re-opened?
The bug still exists on 15.04 on a Lenovo M30-70.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320070
Title:
Realtek Wifi card RTL8723BE drops connection with
Bug still present in Trusty (14.04 LTS).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/180551
Title:
Postfix myhostname defaults to uname() not gethostname().
To manage
Bug still present in Trusty (14.04 LTS).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/180551
Title:
Postfix myhostname defaults to uname() not gethostname().
To manage notifications about this
Upstream bug: https://sourceforge.net/p/awstats/bugs/914/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awstats in Ubuntu.
https://bugs.launchpad.net/bugs/908901
Title:
awstats confused by 408 entries in apache log files
To
601 - 700 of 4874 matches
Mail list logo
