Public bug reported:
This is not a bug, but a feature request.
At the moment it is not clear if run-one exited with return value 1 or
the command failed with return value 1, e.g.:
$ run-one bash -c 'sleep 5; exit 1'; echo $?
The return value will always be '1', but I want to know, if run-one
re
Thanks for following up on this.
I have to get some work done with xournal and matter working. As soon
as I find some time, I will follow the steps in comment #1, but it might
be only on or after the weekend...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi there,
thanks for your reply. In the meantime I found this bug report
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7587
and this
https://gitlab.gnome.org/GNOME/mutter/-/issues/3372
which address the issue.
For now I downloaded the new mutter packages from
http://archiv
Public bug reported:
See
https://github.com/xournalpp/xournalpp/issues/5719
for a full description.
While the bug can be triggered or caused by xournalpp, gnome-shell
should not crash, but hand it gracefully.
Short excerpt from 'journalctl':
Jun 11 10:51:10 my-hostname gnome-shell[7110]: G
So what is the 'proper way' of raising the priority of this bug? It is
clear that this bug should have the highest priority and a fix should be
included with the normal updates and not just a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I can confirm the problem with the workspacre switcher with many windows
open.
Related to https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/760814
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/7
Why is this still marked as 'new'? It is a simple clarification of the
bash info-pages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591677
Title:
bash documentation about BASH_LINENO and BASH_SOU
I have exactly the same problem. I try to open a pptx file X crashes.
In the file Xorg.0.log.old you can find:
Backtrace:
[45.654] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80ef31b]
[45.654] 1: /usr/bin/X (0x8048000+0x5d00d) [0x80a500d]
[45.654] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x
This is the new bug report
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/591677
--
BASH_SOURCE is not correct
https://bugs.launchpad.net/bugs/318678
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: bash
The bash manual should be updated with something like the following.
For more details see
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/318678
`BASH_SOURCE'
An array variable whose members are the source filenames where
the corr
Ok. I will do that then. Thanks for catching the typo.
--
BASH_SOURCE is not correct
https://bugs.launchpad.net/bugs/318678
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
Lesmana Zimmer wrote:
> the bash manual says that BASH_SOURCE shows filename where a function is
> defined
> (and not the filename from where the function is called).
No, this is not true. Nowhere it says that BASH_SOURCE holds the
filename where FUNCNAME is _defined_. In fact, the documentat
There is another problem, but only when the laptop runs on battery.
There seems to be some time limit for entering the password after
suspend. After that limit the laptop goes to sleep again.
So, due to the long time it takes to resume, I sometimes just see the
login screen for 1-2 seconds before
I should add the computer was booted directly from a Karmic CD.
--
slow resume after suspend to ram
https://bugs.launchpad.net/bugs/484183
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.ubu
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/35783089/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/35783090/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/35783091/BootDmesg.txt
** Att
Public bug reported:
>From the dmesg output it seems that there might be a problem with device
>MAT0019:00.
It failed to resume and it also seems to take a long time.
[ 315.780104] sdhci-pci :06:00.1: restoring config space at offset 0x3
(was 0x80, writing 0x802010)
[ 315.780122] sdhc
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/34972347/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/34972348/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34972349/BootDmesg.txt
** Att
Public bug reported:
Slow resume after suspend.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Ana
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/21350658/Dependencies.txt
--
BASH_SOURCE is not correct
https://bugs.launchpad.net/bugs/318678
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Public bug reported:
Binary package hint: bash
BASH_SOURCE shows filename where a function is defined and not the
filename from where the function is called.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: bash 3.2-4ubuntu1
ProcEnviron:
PATH=/home/username/soft/bin:/hom
See also https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/109712.
--
gnome crashes upon relogin
https://bugs.launchpad.net/bugs/109357
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@list
I can confirm this.
See https://bugs.launchpad.net/ubuntu/+bug/109357/comments/4
See https://bugs.launchpad.net/ubuntu/+bug/109357. This is the same bug.
--
Killing X with Ctrl-Alt-Backspace multiple time corrupt the display when using
the vesa driver with a Q965 graphic controller
https://bu
I can confirm this behavior.
I use a Dell Optiplex 745 with a 965Q graphics (with the i810 driver).
Switching to the console works, but switching back to the X server results in a
messed up display.
Under edgy the display would sometime blink and flicker with strange things
appearing when moving
23 matches
Mail list logo
