Public bug reported:
Rationale
There is currently no C++ compatible logging package in main.
Canonical projects that require logging should not be resolving the
requirement.
The mir project is an an example - and glog seems the most lightweight
solution to its logging requirements. As
For raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1151844
Title:
[MIR] google-glog
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gflags/+bug/1151844
Looking at glog ftbs on armhf I see a stack trace with
"__libc_do_syscall" where "DieInThread" is expected.
Googling says others see the same but I don't yet understand what's
going on. Is the stack frame different on armhf?
--
You received this bug notification because you are a member of Ubunt
Looks like the failing test is x86/x86_64 specific. Can we patch?
=== modified file 'src/signalhandler_unittest.sh'
--- src/signalhandler_unittest.sh 2012-06-21 21:07:21 +
+++ src/signalhandler_unittest.sh 2013-03-13 14:15:15 +
@@ -72,6 +72,13 @@
exit 0
fi
+# The symbols
Public bug reported:
Building on ARM fails test:
$ make check-TEST
...
./src/signalhandler_unittest.sh
'DieInThread' should appear in the output
make[3]: *** [signalhandler_unittest_sh] Error 1
make[2]: *** [check-am] Error 2
c.f. http://code.google.com/p/google-glog/issues/detail?id=140
** Aff
** Changed in: compiz-core
Assignee: Alan Griffiths (alan-griffiths) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833729
Title:
compiz crashed with SIGSEGV
*** This bug is a duplicate of bug 932125 ***
https://bugs.launchpad.net/bugs/932125
** This bug has been marked a duplicate of bug 932125
compiz crashed with SIGSEGV in Glib::Source::prepare_vfunc()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Unfortunately the fix - https://code.launchpad.net/~alan-griffiths
/compiz-compizconfig-gconf/Bug-953214-revised - didn't actually get
packaged as intended. Is being corrected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~vanvugt/compiz-core/fix-alt-bugs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944979
Title:
Quicklist are not showing if right-clicking a launcher icon in Expo
mode if trigg
On 23/02/12 00:43, Sam Spilsbury wrote:
> This crash only happens when DISPLAY= is not set. As such, compiz would
> fail to start anyways.
I assume from this the desired outcome is a graceful exit?
--
Alan Griffiths +44 (0)798 9938 758
Octopull Ltdhttp://www.octopull.co.uk/
-
** Branch linked: lp:~alan-griffiths/compiz-core/bug.936487
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936487
Title:
compiz crashed with SIGSEGV in XDefineCursor()
To manage notifications about
I can't prove that all instances of this fault have the same cause, but
there is an issue that the shift switcher exposes when right click is
processed.
There's a fix committed by Łukasz to the shift switcher to remove an
unused "Terminate" option, and I'm working on core to prevent plugins
that e
** Changed in: compiz (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/808007
Title:
compiz crashed with signal 5 in Glib::exception_handlers_invoke
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867361
Title:
Nvidia graphics fail to start on 20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net
Public bug reported:
System is a Slimbook ProX15.
Nvidia graphics work with 18.04/435, but with 20.04 the system doesn't
come up (tried both 440 and 435).
It looks as though the Nvidia card is active, but there are no outputs
attached to it.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
** Changed in: mir (Ubuntu)
Status: In Progress => Invalid
** Changed in: mir
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728931
Title:
[testsfail] S
** Changed in: mir
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728581
Title:
"mir_demo_server --help" does not show help text
To manage notifications a
gtk-mir is no longer a thing
** No longer affects: unity8 (Ubuntu)
** No longer affects: qtmir (Ubuntu)
** No longer affects: mir (Ubuntu)
** No longer affects: gtk+3.0 (Ubuntu)
** No longer affects: miral
** No longer affects: mir
** Changed in: canonical-devices-system-image
Status:
** Changed in: mir (Ubuntu)
Status: In Progress => Invalid
** Changed in: mir
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523621
Title:
[ FAILED ] Nested
** Changed in: miral
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420334
Title:
[enhancement] Missing client API for relative surface movement (e.g.
dragg
501 - 520 of 520 matches
Mail list logo
