Hi Alberto,
Thanks for compiling all this information. There's a couple of pieces
missing though.
This bug doesn't happen as far as I know with vanilla Gtk. It happens
when the Unity Gtk extensions (dbusmenu and overlay scrollbar) are
loaded. They are Gtk plugins and one or both of them open
@mspacek
The unity-gtk-module packages are the trouble makers in this particular
case, per the UBUNTU_MENUPROXY should not be set in Xfce bug. But
that's only half the problem and having those loaded in Xfce causes
other problems. The late fork() problems can potentially be triggered by
other
There is a much easier workaround. Just copy the files with terminal, or
another file manager that isn't Nautilus. As such, I don't believe this
is a fault with bluez or even gvfs, but with Nautilus or some other
Gnome component.
The really easy way to do it with Terminal:
cd to the destination
Today my workaround didn't work. This suggests the problem is in gvfsd
or obex-data-server.
** Also affects: obex-data-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gvfs (Ubuntu)
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172995/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172994/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172996/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172993/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172997/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173002/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173001/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4173000/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1284308/+attachment/4172998/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
This patch causes an annoying g_critical if you add a grab on a widget
before it is realized. In this case toplevel-window will be null.
This also make me wonder what happens if you add a grab to an offscreen
widget before realizing it.
--
You received this bug notification because you are a
Did you attempt to add the indicator-menu (global menu indicator)?
Because that does not work, will crash like this, and is unsupported.
** Also affects: xfce4-indicator-plugin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
See screenshot.
Open should be Open a torrent
Open should be Open URL
Pause should be Pause all torrents
Play should be Start all torrents.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu in Ubuntu.
Just for the record this still affects trusty, including transmission
which is a default app.
** Attachment added: transmission menu
https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1270486/+attachment/4312122/+files/tm.png
--
You received this bug notification because you are a
The bug still appears in vivid/xfce from about 3 days ago.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdbusmenu in Ubuntu.
https://bugs.launchpad.net/bugs/1270486
Title:
indicator-application doesn't use the menu
Still broken in 15.04.
** Changed in: cups (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1181423
Title:
Cannot print at all with USB
** Attachment added: cups error log
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1181423/+attachment/4437636/+files/error_log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Public bug reported:
1. Install ubuntu-desktop-16.04-amd64
2. sudo apt-get update && sudo apt-get install unity8-desktop-session-mir
3. Reboot.
4. Log in to unity8 session.
Result: black screen, no mouse pointer. The screen backlight dims after
a while.
Reporting yet another new bug to try to
** Attachment added: "unity8.log"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1573292/+attachment/4642061/+files/unity8.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
*** This bug is a duplicate of bug 1549455 ***
https://bugs.launchpad.net/bugs/1549455
** This bug has been marked a duplicate of bug 1549455
Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT:
"eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
--
You received
I have an Atom N455 convertible with Pineview graphics. Unity8 session
just displays a black screen forever. Unity 7 works fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
This bug happened to me today. I found an easily reproducible bug in a
package, so because I am a helpful person, I did a fresh install just to
repro it in +1, and submitted a core dump through apport. Because I knew
for a fact that there was no private information in the clean install I
set my
Public bug reported:
I'm not sure if this is reproducible but this is what I did:
1. Enter Ubuntu One account details through system settings -> online accounts.
2. Open the app store from the main app scope.
3. Install Popey's Youtube app and then "open" it from the app store page.
4. Play
Also the first time I encountered the side stage was after opening the
weather app and then rotating to landscape mode. The weather app
automatically puts itself into the side stage, obscuring the message
about three finger dragging.
--
You received this bug notification because you are a member
+1 the area you need to hit is so small that it takes several attempts
even if you know exactly what you are aiming for. If you just guess that
maybe you can swipe away the side stage then your chances of actually
hitting the absolutely tiny region where it works are virtually nil.
--
You
Just because the upstream report was marked as a duplicate, does not
mean it is invalid.
** Bug watch added: GNOME Bug Tracker #762252
https://bugzilla.gnome.org/show_bug.cgi?id=762252
** Changed in: gtk
Importance: Medium => Unknown
** Changed in: gtk
Status: Invalid => Unknown
The same messages are logged on the live image boot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1754836
Title:
Failed to activate service
Status in bluez package in
** Attachment added: "log running blueman-applet manually"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077985/+files/blueman-applet-manual.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Summary changed:
- Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez':
timed out (service_start_timeout=25000ms)
+ ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
There is more stuff in syslog too. It looks like pulseaudio is trying
and failing to start blueman.
** Attachment added: "cat syslog | grep -E '(pulseaudio|blueman)'"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077997/+files/syslog.txt
--
You received this bug
No, we are talking about the errors in xsession-errors.txt:
ERROR:dbus.proxies:Introspect error on org.bluez:/:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ERROR:dbus.proxies:Introspect
*** This bug is a duplicate of bug 1749546 ***
https://bugs.launchpad.net/bugs/1749546
The Bluez timeout errors still show up in ~/.xsession-errors at least on
hardware without Bluetooth. However, it seems to be harmless.
--
You received this bug notification because you are a member of
As far as the original bug with delayed login goes... it seems that the
Bluetooth stuff is a red herring.
Since it only happens on first login, I deleted the contents of ~ and
relogged. The delay came back, so I bisected the files until I arrived
at the single file which needs to be deleted in
seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1754836
Title:
Xubuntu: ERROR:dbus.proxies:Introspect
Another piece of the puzzle: if you run:
sudo fc-cache -fv
this will rebuild the system font cache in /var/cache/fontconfig
If you then delete the user's cache in ~/.cache/fontconfig and re-log,
there is no delay... and the user's font cache will NOT be rebuilt.
After a delayed login,
Some more: touching the system cache files doesn't make it work.
Binary diff on the cache files before and after running fc-cache shows
this:
63 c7 c3 5a 00 00 00 00 47 72 ce 15 00 00 00 00
63 c7 c3 5a 00 00 00 00 00 00 00 00 00 00 00 00
Before, at offset 0x38, the "bad" cache files have
One final thing: this does not affect Ubuntu desktop after install. But
it does affect the Ubuntu live image, which takes an extra minute or so
to boot. It seems that the Ubuntu desktop installer rebuilds the system
font cache during install.
--
You received this bug notification because you are
On the current daily ISO this now hangs for 50 seconds instead of 75,
and the blueman/bluetooth messages are completely gone from xsession-
errors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I tried to log in over ssh and run top so I could watch which processes
were running but this caused the delay to disappear.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Since this only happens on first login, I ran a diff on the full home
directory before/after login:
https://paste.ubuntu.com/p/SJ2nNx7WfP/
I don't see anything obvious in there. The pulse cookie and a blueman
settings file (empty) were created. The rest seems to be Thunar/desktop
defaults and
I have Bionic/18.04/glib 2.56 and this bug still happens.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1332623
Title:
Thunar behaves inconsistently with USB flash drive
Since installing 23.04 I can no longer print at all. Attempting to print
anything from any application makes the printer display "Error 49 - Turn
off and turn on again" on the display, and then reboot itself. This was
a clean install.
Older versions of Ubuntu continue to print at the correct size
** Attachment added: "No sound cards"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1992254/+attachment/5622336/+files/no-sound-cards.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
I just rebooted my computer and now my sound card, which has worked
perfectly well for the past 5 or so years, apparently no longer exists.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic
I rebooted and everything came back?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1992254
Title:
PCI/internal sound card not detected
Status in alsa-driver package
The full upgrade logs are available on bug 1985966 which I have marked
as a duplicate of bug 1969786.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1985964
Title:
Public bug reported:
While attempting to do-release-upgrade from 20.04 to 22.04, the upgrader
crashed, and then the problem report script also crashed, leaving behind
a corrupted crash report in /var/crash. This bug is about the problem
report crash. I will report the upgrader crash separately.
In order to work around this I first printed my labels to a PDF file in
LibreOffice, then printed that file with 101.5% scaling.
I had to do it this way because LibreOffice does not use the standard
printer dialog - the scaling option is not shown.
--
You received this bug notification because
Public bug reported:
To reproduce:
1. Open Inkscape.
2. Draw a rectangle 170mm x 230mm.
3. Print it.
Expected result:
The printed rectangle on paper should measure 170mm x 230mm.
Actual result:
The rectangle measures 168mm x 226mm, a difference of approximately 2%.
I print a lot of labels.
** Attachment added: "Test SVG"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5635061/+files/170x230.svg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
I tested printing a PDF with `lp -o print-scaling=none 170x230.pdf`. The
PDF and source SVG are attached. The resulting rectangle is still 168mm
x 226mm.
** Attachment added: "Test PDF"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5635060/+files/170x230.pdf
--
You
Inkscape and Atril both have the same print dialog. It looks like the
attached screenshot. Notice "Scale" is set to 101.5%. This is the only
way I can get either of them to print at the correct size.
LibreOffice has a different print dialog with no scaling options at all,
hence why I had to print
ppd file
** Attachment added: "testipp.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643436/+files/testipp.ppd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Note that both of the print commands failed to print anything at all,
but the testipp printer does know that my printer is low on toner. Also
I tried deleting the testipp printer and recreating it but still
nothing.
--
You received this bug notification because you are a member of Ubuntu
Touch
error log
** Attachment added: "error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5643437/+files/error_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Also I just tried printing the test document on another computer which
still has Ubuntu 18.04 installed. The output rectangle was undersized by
less than 1mm, which seems okay. I can attach the ppd file and error log
from there if it would help.
--
You received this bug notification because you
Error log from 18.04.
The command I ran was:
lp -d HP_LaserJet_100_colorMFP_M175nw_61F41D_ -o print-scaling=none
170x230.pdf
I also previously tried it without the print-scaling option (not
logged), and result was the same. Very close to the correct size both
times.
** Attachment added:
PPD file from 18.04. The MD5 does not match the other one so it is
definitely different somehow. Note that the name is nearly identical but
has an extra underscore at the end for some reason.
Also there are two print queues for this printer on the old machine. I
didn't try the other one. It's PPD
error log
** Attachment added: "var_log_cups_error_log.txt"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5642940/+files/var_log_cups_error_log.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Launchpad throws an error whenever I try to attach the ppd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1998917
Title:
Everything prints approximately 2% too small after
test
** Attachment added: "170x230.pdf"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5642941/+files/170x230.pdf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Okay well it seems to be specific to the PPD file. I wonder why it won't
accept it. I tried adding ".txt" to the filename too but it still
wouldn't accept it. Must be due to the contents.
Anyway that's the PDF I used to test (same as previous one) and I used
the lp command line invocation.
I'll
So attaching the PPD to my bug report about not being able to attach it
seems to have fixed the problem, and now I was able to attach it here.
:)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
ppd
** Attachment added: "HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1998917/+attachment/5642945/+files/HP_LaserJet_100_colorMFP_M175nw_61F41D.ppd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The printer has firmware 20111021. The newest available firmware is
20140618 but can only be installed through Windows.
This printer always reports low toner and I ignore it because it will
continue printing with no loss of quality for hundreds of pages, usually
several times what I already
68 matches
Mail list logo
