For info.
The bug also means that the systemd journal is growing at an extremely
fast rate. Double whammy. All these files by default reside in the root
file system. Which is usually created quite small.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1944397 ***
https://bugs.launchpad.net/bugs/1944397
Daniel,
I am not sure this is the same bug. I am getting this in Hirsute after a
recent kernel update.
The warnings appear to be in a different area than those in #1944397
3437:Sep 29 15:33:29 brubeck
I am also seeing this after an automatic update from linux-
image-5.11.0-1017-raspi to linux-image-5.11.0-1019-raspi. The display
output is lost very early on in the boot process.
The only way I could get round it was to roll the kernel back to
5.11.0-2017.
Roger
--
You received this bug
Try
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/comments/18
It worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932328
Title:
Thunderbird under Wayland does
Public bug reported:
Frequently leaves an open window marker on the Thunderbird icon in Gnome
Desktop favourites sidebar. This is especially prevalent when the
program has been launched as the default email client by some other
process. Right clicking on the icon brings up the "New window/Compose
Daniel,
I apologise.
We have been talking about different apps. I have been referring to the
browser plugin that talks to https://extensions.gnome.org/. This is
because it was the first thing I spotted when I searched on the net. I
realise that what you have been talking about the is a
I am running Ubuntu Focal 20.04. The gnome-shell version is
3.36.2-1ubuntu1-20.04.1. The desktop icons version is
20.04.0-2-1ubuntu1-20.04.1. The app does not work. I believe the app is
designed to work on per user extensions only.
The desktop icon extension is installed as a system extension in
The Extensions app does not appear to work fro the csoriano version of
desktop icons. It thinks that it is the rastersoft fork.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872796
Title:
If you are experiencing this bug. Try the following.
if the directory "/usr/share/gnome-shell/extensions/desktop-
icons@csoriano" rename it to something else. Then restart the desktop
(logout then login).
Please report the results of this test back here.
I am trying to correlate information on
If you are experiencing this bug. Try the following.
if the directory "/usr/share/gnome-shell/extensions/desktop-
icons@csoriano" rename it to something else. Then restart the desktop
(logout then login).
Please report the results of this test back here.
I am trying to correlate information on
If you are experiencing this bug. Try the following.
if the directory "/usr/share/gnome-shell/extensions/desktop-
icons@csoriano" rename it to something else. Then restart the desktop
(logout then login).
Please report the results of this test back here.
I am trying to correlate information on
This bug is still present in Focal. It seems to have lost focus in
upstream. In Focal it is much harder to remove the extension as it is
even more tightly linked in as a mandatory dependency for a number of
major system components. The only way to remove it is by deleting or
renaming its files.
I am seeing a version of this bug in 19.04.
However, this also causes a corruption of the of the cupsd.conf file and
subsequent failure of the cups service to start/restart.
The cupsd.conf filer is overwritten with the single line.
PreserveJobFiles Yes
I think this deserves more urgency than
I have now reinstalled the extension and having been running for a day
without problems. This leads me to think that this a persistent data,
rather than code related problem. I can only assume that the purge
reinstall cycle removed whatever was causing the problem.
--
You received this bug
The extension is only fully removed if you purge it and reboot your
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812883
Title:
Desktop view flashes every time ~/Desktop changes
To manage
Hi Jonathon,
Sorry, I wasn't clear. I really only meant the uninstall as a temporary
test, to provide more information on what issues this extension was
causing. For me it also solved a number of seemingly unrelated issues
mostly to do with excessive cpu usage.
Roger
On 19 August 2019
** Changed in: network-manager (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/1532431
Title:
NetworkManager interferes with unmanaged 802.11 monitor mode
** Changed in: libexosip2 (Ubuntu)
Status: New => Invalid
** Changed in: linphone (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/1704577
Title:
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-ati (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/1746232
** Changed in: jackd2 (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/892918
Title:
Cannot start jack using qjackctrl via dbus when playback only option
is
I think this bug may well be a duplicate of #1825623. Would anyone
object if I marked it as such.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812883
Title:
Desktop view flashes every time
I worked round this issue by uninstalling gnome-shell-extension-
appindicator. This fixed this issue and also a number of high cpu usage
issues I was seeing. The cpu issues were sometimes severe enough to also
expose weaknesses in the compositor.
I suggest that anyone who is getting problems with
Closed bug to reduce confusion.
** This bug is no longer a duplicate of bug 1812883
Desktop view flashes every time ~/Desktop changes
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have seen a number of issues related to this error message. Including
slow wake up from sleeps. Long pauses in screen repaint. Long launch
times for applications. The only sure fix I found was to completely
purge the gnome-shell-extension-appindicator package and reboot. The
system them becomes
*** This bug is a duplicate of bug 1826604 ***
https://bugs.launchpad.net/bugs/1826604
Hi Daniel,
Sorry about the incomplete bug report. I had forgotten that I had turned
apport. I have now found a fix for the first part of my report. This has
reduced the noise level so that I can see the
Public bug reported:
When I close a window on the gnome desktop. The desktop often freezes
for anything between 30 seconds and a number of minutes. I notice this
most often when closing a terminal window with ctrl+d.
When look at the syslog and cpu usage (top) from a terminal logged in
via ssh I
The p2p-disabled flag is not supported until wpa-supplicant 2.5+.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769231
Title:
wpa_cli -i flag and p2p_disabled=1 config broken
To manage
I have raised this bug at
https://bugzilla.kernel.org/show_bug.cgi?id=198669
** Bug watch added: Linux Kernel Bug Tracker #198669
https://bugzilla.kernel.org/show_bug.cgi?id=198669
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The file name above should read radeon_ring.c. I thought you used to be
able to edit comments on here!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746232
Title:
driver looping then crashing
To
Oops I meant to say "which probably should be reassigned to this
package."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301649
Title:
BUG: unable to handle kernel paging request at
This crash looks very similar to #1301649. However is does not require
the system to go into power save.
The crash is in radeon_ring_backup which is in
linux/drivers/gpu/drm/radeon/radeon_device.c and part of the linux
(kernel) package.
I have added that package to this bug.
--
You received
** Also affects: linux (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/1746232
Title:
driver looping then crashing
To manage notifications about
I am also seeing the same crash when running Ubuntu 17.10 with the Gnome
desktop using the xwayland compositor. This manifests in a slightly
different way. It does not require the screen to turn off. It can occur
randomly at any time, usually when the system is idle. I am currently
get one or two
Public bug reported:
Running driver on Artful with the xwayland compositor. At random times
the GPU stalls with.
Jan 30 11:22:28 dragon kernel: [ 487.046219] radeon :02:00.0: ring 0
stalled for more than 29200msec
Jan 30 11:22:28 dragon kernel: [ 487.046224] radeon :02:00.0: GPU
It only takes a single null character to throw geany. Attached a simple
test file.
** Attachment added: "Simple test file with one null character amidst some
text."
https://bugs.launchpad.net/ubuntu/+source/geany/+bug/738672/+attachment/5020676/+files/geanytest
--
You received this bug
I have raised this on Gnome Bugzilla. Bug number #787645.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504079
Title:
tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
To manage
My workaround for ubuntu setups. Is to put a file called .trackerignore
in any directories that contain avi files. The default configuration for
tracker appears to set this.
gsettings get org.freedesktop.Tracker.Miner.Files
ignored-directories-with-content
['.git', '.trackerignore']
The bug
Also happening in 17.04. Started happening after a fsck repair following
a power failure. Could be related to lost/corrupt files.
Running tracker-extract manually on file shown in syslog gives the
following.
roger@dragon:~/Documents/Old Stuff/Camtasia Studio$ tracker extract
Public bug reported:
Linphone on ubuntu is patched to use the libexosip2 library rather than
libbellesip. The current libexosip2 package does not appear to handle
the lookup of voip DNS SRV records correctly. The causes the handling of
sip uris when not using an outbound proxy to be broken.
For
I am changing the name of this bug and reopening it because the problem
with the invalid ppd file still exists.
The make-duplex-page-sizes-default.sh generates causes bad ppd files to
be generated for the following printers.
hp-officejet_6800.ppd: FAIL
hp-officejet_pro_6830.ppd: FAIL
This could well be a problem with your apt-sources.list. Make source you
have the ubuntu-updates repository activated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586887
Title:
Can't install
I have upgraded to Xenial and I can no longer reproduce the original
bug. I can only assume it was something in gtk+ this has been fixed in
Xenial. The fact that when it happened the jobs stuck in the queue
unless deleted with the only evidence that anything was amiss being the
lack of print
I thought I had posted a reply but i obviously had not.
I had already tried the the test you suggested.
I built a 3.15.7 version the hplip package with the make-duplex-page-
sizes-default.sh script disabled and reinstalled with that. The
hpcups.drv work fine for duplex printing with A4.duplex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568996
Title:
Duplex printing does not work properly for HP printers
To manage notifications about this bug go to:
I spelt constraints correctly in the next version and it still does seem
to be doing anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568996
Title:
Duplex printing does not work properly
On 18/04/16 04:41, Till Kamppeter wrote:
> Perhaps we need to remove the script to return to upstream reality with
> the original awkwardness (perhaps this could be the SRU for Xenial) and
> for a more sophisticated solution pre-build all PPDs, edit them with a
> script to rename the paper sizes,
Ok. I understand the need for the {0,4} now!
Unfortunately in the 6510 ppd definition in the drv file the .Duplex
defintion is 102 lines further down the file.
I will test with a value to compensate for that. But I still think that
this is just sticking a bandage on a bandage.
I found a note
The attached script is a work in progress. The CustomMedia stuff is
working but the UIConstraints is not.
I have tried to make it as simple and clear as posible but I have more
work to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Script to replace the original"
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4638301/+files/mds-rfj.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well I found one problem in the script. But unfortunately it does not
fix the problem.
the line
duplexsizes=`grep -v '^//' $f | grep CustomMedia | grep '\.Duplex' | cut
-d " " -f 4 | cut -d "/" -f 1 | cut -d '"' -f 2 | perl -p -e
"s/\.Duplex//" | sort | uniq`
does not match all of the
"{0,100}?". No change same failures.
"*?" Lots more failures.
Not done any tests with bigger than 100, the request is too open ended!
Is it time to reassess this approach? I suggest we ensure that the DRV
file is correct at package build time and push the required changes
upstream. Running a
** Attachment removed: "The cut own version of the original hpcups.drv file"
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635423/+files/6510.drv.orig
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "The script form Xenial source (looks unchanged since
2010)"
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635428/+files/make-duplex-page-sizes-default.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "The cut own version of the original hpcups.drv file"
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635427/+files/6510.drv.orig
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "The cut down version after running script"
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1568996/+attachment/4635424/+files/6510.drv.munged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The version on Xenial is hplip-3.16.3+repack0
I have cut out the bits of the Xenial hpcup.drv file that generate the
ppds for the 6510 and other Copperhead printers, and used them to run
some tests.
These show that the make-duplex-page-sizes-default.sh (from Xenial)
fails to rename the original
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568996
Title:
Duplex printing does not work properly for HP printers
To manage notifications about this bug go to:
Just realised that I still have not got the wording right in the
description regarding the workaround. I think a simpler workaround given
the current layout of the hpcups.drv file is just to remove the first
occurence of each the duplicated pagesize and PageSize and PageRegion
lines in the ppd and
Hi Till,
Just tested with a Xenial live dvdrom. Yes the problem is still there.
Looks like the same list of printers.
Roger
On 12/04/16 17:48, Till Kamppeter wrote:
> Can you please test (with a live CD or USB stick) whether the problem
> persists in Xenial (Ubuntu 16.04 LTS)? Thanks.
>
>
> **
So... after looking at that debian/local/make-duplex-page-sizes-
default.sh again and remembering why I hate perl.
I decided that this bug should probably be changed to:
The make-duplex-page-sizes-default.sh generates causes bad ppd files to
be generated for the following printers.
I have changed the original bug text slightly. After spending some time
grepping the cups and gtk source to find what was adding the .Duplex
suffix I realised it was probably coming from my own changes and I had
copied the wrong bit of log into the bug. The problem is still that it
is the second
** Description changed:
I am reporting this as a new bug because I want to avoid adding further
to the mish mash of half fixed bugs that is duplex printing on hp
printers via cups.
I will warn readers that this will sound like a bit of a rant. But these
issues have been outstanding
Public bug reported:
I am reporting this as a new bug because I want to avoid adding further
to the mish mash of half fixed bugs that is duplex printing on hp
printers via cups.
I will warn readers that this will sound like a bit of a rant. But these
issues have been outstanding for years
1.
Attached a NetworkManager log showing what happens when the interface is
deleted.
** Attachment added: "Network Manager log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+attachment/4547334/+files/test.log
--
You received this bug notification because you are a
Public bug reported:
If a virtual 802.11 interface of type monitor is created on a 802.11
physical interface that already has a virtual interface of type managed
created on it, then the managed interface is deleted. NetworkManager
sets the type of the monitor interface to managed. This can be
Just a quick comment. I know this was mentioned before (#46) but it
would be a good idea if everyone checked this behaviour with phone in
both locked and unlocked states _before_ it is plugged into the USB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Jon,
Do you have a screen lock (pin etc.) active on your phone? If so do you
see any difference in behaviour between connecting your phone when it is
unlocked and connecting it when it is locked?
Roger
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same problem on 15.04 with an HTC Desire 820. Unable to mount android
phone message and then an empty nautilus browser window. Is this
something to do with the transient usb mass storage device that phones
with this chipset reports on the usb bus for a while after first
connection. This is
I am also seeing this problem with my HTC Desire 820. I think this is a
duplicate of #1314556
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1453479
Title:
Unable to mount Android Phone since
I have just started seeing this or a simlar problem on Ubuntu 14.04.
Syslog shows that the device has been detected corrected as not being
write protected.
Mar 31 19:12:10 dragon kernel: [ 8964.742391] sd 4:0:0:0: [sdb] 61863936
512-byte logical blocks: (31.6 GB/29.4 GiB)
Mar 31 19:12:10 dragon
** Changed in: hplip (Ubuntu)
Status: New = Incomplete
** Changed in: hplip (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422007
Title:
I have closed this as invalid while I do more work investigating. Using
the latest version of hplip improves things. Then only a very small
amount is clipped off the bottom. This may be a local printer hardware
related problem.
However the main reason I raised this bug was to clean away some of
Public bug reported:
The default hpcups driver ppd for HP Photosmart 6510 printers when used
with the A4.Duplex PageSize (or any other related PageSize) shifts the
Postscript userspace coordinate system 3mm up the page on all pages of
single sided prints and on odd numbered pages of duplex
Can someone please reopen this bug!
I have just tried the test file I attached 18 months ago again. The
margins are even more broken now! Printing the test with shrink to fit
enabled shows a 15mm clip at the top and bottom and 4mm each side in
both single sided and duplex modes on A4.
This
Aarrg.
Even hpijs is broken now as well. But it is broken in exactly the same
way. Does it mean the problem is somewhere upstream from cups?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/405116
This bug also affects me. I just want an interface that nothing is sent
out on and with no addresses, for my switch's monitor port.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314848
Title:
not
For a more comprehensive fix that catches all the cases where warning
are generated when the global intrepreter lock has been released and
_PyThreadState_Current set to NULL, you can try the following patch to
pygobject-2.
--- pygobject-2-2.28.6.orig/gobject/gobjectmodule.c
+++
I switched to trying to resolve my case of the bug by fixing the cause
of the warning. In my case this is a warning from pango that it could
not find a loadable module.
/usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot
open shared object file: No such file or directory'
The
Here is a slighlty more informative gdb run with the python-qt4 debug
symbols loaded.
You can see from this that the crash occurs because the qt4 sip code
calls
Py_BEGIN_ALLOW_THREADS
This sets _PyThreadState_Current to NULL, and then
sipCpp = new sipQApplication(nargc, argv);
Somewhere in
I suspect that this is happening because python has hooked itself if
into the GTK logging system. So it looks like _PyErr_WarnEx should
really check whether _PyThreadState_Current is non NULL before
proceding. This rreally looks like a horrible can of worms.
Can the python guys please look at
I had a quick try with python-dbg but got some error messages very early
one in the initialisation process. I have not looked into them any
further.
However I have no do a run with a hardware break point on
_PyThreadState_Current. This show that it is the /usr/lib/python2.7
This looks like a bug in the python interpreter.
The routine setup_context in Python/_warnings.c looks like this.
setup_context(Py_ssize_t stack_level, PyObject **filename, int *lineno,
PyObject **module, PyObject **registry)
{
PyObject *globals;
/* Setup globals and
This bug is still affecting me in 14.04.
Have looked at this further using gdb. It seems that there is a generic
problem in do_warn when called from systray.py. A number of other bugs
have reported this with different warning messages cuasing the crash. So
anything that causes a warning message
This bug has many duplicates. It appears that systray.py will crash
whenever a warning message is generated. The oither bugs report a number
of different warning messages.
The following bugs are definite duplicates.
#862779
#1046036
#1046635
#1157504
#1287596
#1299676
#1299764
The following are
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug is no longer a duplicate of bug 862779
systray.py crashed with SIGSEGV
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug is no longer a duplicate of bug 862779
systray.py crashed with SIGSEGV
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug still exists on 14.04 Trusty Tahr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860680
Title:
systray.py crashed with SIGSEGV
To manage notifications about this bug go to:
Still happening at 14.04. Managed to do apport-retrace and run gdb. This
is what the stack trace looks like now. It may be another bug is hiding
the first one.
info (gdb)Auto-loading safe path
done.
warning: core file may not match specified executable file.
[New LWP 6922]
[New LWP 7063]
I think there are a number of bugs here.
The version I see is.
With Turn screen off when inactive set to 30 minutes and Suspend when
inactive for set to 1 hour. If I come back after an hour the screen has
turned off, but the computer has not suspended. When I wake up the
screen the dekstop has
Just upgraded to 13.10 and am getting this on every login. It was
working fine on 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/632066
Title:
systray.py crashed with SIGSEGV in
Some additional info. I ran some more tests using the hpijs driver and
duplex printing on a Photosmart 6510, and there is still a 5mm clip of
the top margin on when duplex printing a test pdf file using evince.
This occurs irrespective of whether Shrink to printable area or Fit
to printable area
I can confirm that this bug is still present in 13.04. Using the add
printer function from the desktop gui to find a network connected HP
Photosmart 6510 and accepting all the defaults, results in a
configuration which clips at the top and bottom margins. The simple fix
is to go into the printer's
Sorry about the crazy spelling, I think my s key must have gone missing!
The next to the last line should read.
Starting a jackd without the playback only parameter always results in
a server that hangs and does not respond to any client requests.
--
You received this bug notification because
1 - 100 of 103 matches
Mail list logo
