[Bug 1881893] Re: Gtk3 crashes, icon "image-missing" not in theme Symbolic
This is a packaging issue. The icon for "missing", which is in package gnome-icon-theme, MUST be installed with GTK. The icon for "missing" is the fallback icon for GTK whenever it can't find an icon. If GTK package does not depend on gnome-icon-theme, then GTK will crash when it needs the icon for "missing." ** Package changed: ubuntu => gnome-icon-theme (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881893 Title: Gtk3 crashes, icon "image-missing" not in theme Symbolic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1881893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881893] [NEW] Gtk3 crashes, icon "image-missing" not in theme Symbolic
Public bug reported: Context: Ubuntu 19.04. I am a developer running a Gimp plug-in (Python) in the Gimp app. Opening a Gtk.FileChooserButton widget. Expected widget to appear. What happens: widget is garbled and console shows: Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Icon 'image-missing' not present in theme Symbolic (gtk-icon-theme-error-quark, 0) with a stack trace and opportunity to exit the plugin. Gimp continues to run (since plugin is separate process.) See the issue filed against Gimp: https://gitlab.gnome.org/GNOME/gimp/-/issues/2029. That report is on Gimp in Ubuntu 18.04. Still present with the latest Gimp (built myself) on Ubuntu19.04. Installing the package gnome-icon-theme fixes the issue. As reported in Gimp #2029 It might be a packaging issue: a missing dependency of the gtk3 package on package gnome-icon-theme. Since package Gtk3 can crash unless gnome-icon-theme is also installed. Probably it is a weakness of Gtk3, and would best be fixed there. I.E. its a circularity issue: Gtk3 should not depend on an "image-missing" icon being in a theme to resolve the problem of an icon missing from the theme. Or the Gtk3 developers have failed to convey a dependency to distributors like Ubuntu. ** Affects: 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/1881893 Title: Gtk3 crashes, icon "image-missing" not in theme Symbolic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1881893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324059] Re: file save dialog fails to confirm overwrite existing file
I will file a bug with Qt if you insist, but I think they are already claiming it is not their responsibility, since it is a "native" dialog, that is, provided by the platform's window system, i.e. GTK. So I think it would make more sense to file the bug with the GTK project? If you agree, I will gladly file that bug. I already filed a related bug with Qt: https://bugreports.qt- project.org/browse/QTBUG-38985. (That bug report says that the Save dialog emits too many signals. It is a related bug because it uses the same dialog, although the symptoms are different.) The Qt project already closed that bug, saying the Qt implemented dialog works fine, only the native dialog (implemented by GTK) is broken. Which is the same situation for this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1324059 Title: file save dialog fails to confirm overwrite existing file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1324059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1324059] [NEW] file save dialog fails to confirm overwrite existing file
Public bug reported: I am developing an app using Qt5.2.1, PyQt5, Python3.4 testing on Ubuntu14.04LTS. All packages are Ubuntu packages. When a file exists already, e.g. 'foo.txt'. Start the app which creates files of suffix '.txt'. User creates new document and chooses 'Save'. App displays a file dialog for choosing a filename for saving, passing the default filename of 'untitled.txt'. Filename textbox is empty (incorrectly?). User enters just 'foo' in the filename text box. User chooses the 'Save' button. Dialog incorrectly fails to show a message box to confirm user wants to overwrite existing file. Dialog returns filename 'foo.txt' to the app. App proceeds to overwrite an existing file, causing user loss of data. The QFileDialog by default uses the native dialogs i.e. GTK2? If app instead tells it to use the Qt provided dialog (non-native), the behaviour is as expected (the textbox displays 'untitled.txt' and the dialog confirms overwrite.) (The native and non-native dialogs have different look-and-feel.) This is changed behaviour from Ubuntu 13.04 and Qt4.8. (But I am uncertain whether Qt used the native GTK dialog in those versions.) I have also tested on Ubuntu 14.04Gnome, and the behaviour seems slightly different: depending on whether the user Tabs out of the textbox, the dialog completes the filename in the textbox (i.e. finds the existing file and selects it) and DOES confirm overwrite. (I will need to retest to be sure about this.) Note that I have experienced a related bug, where the dialog emits 'fileSelected' signal twice, once with 'foo' and once with 'foo.txt.' Discussed at qt-project.org forums, but not reported here yet. ** Affects: 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/1324059 Title: file save dialog fails to confirm overwrite existing file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1324059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208129] Re: Compares NoneType() and str(), hence fails to make bootable usb
I experienced this on 13.04. I then downloaded the source package for usb-creator_0.2.47.2 (in raring updates repository) and ran usbcreator- gtk from inside Eclipse. I could not reproduce the error in 3 attempts with various iso images and physical drives. So if you are a user reading this, it might not be fixed because it is hard to reproduce. I think in addition to printing the given error message, the app should also print the python trace. That wouldn't be any uglier to users, and might make it easier to track down the cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208129 Title: Compares NoneType() and str(), hence fails to make bootable usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1208129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068680] Re: Software center does not start [dbus.proxies - ERROR - Introspect error]
I can confirm den.t 's analysis and recommended fix (above). I am a programmer, and futzed with sip and pyqt (downloaded and built a later version than is provided by Ubuntu) and then suffered this problem. If Ubuntu depends so much on Python, Qt, and PyQt, should it sandbox them from developers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068680 Title: Software center does not start [dbus.proxies - ERROR - Introspect error] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-sso-client/+bug/1068680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085425] Re: Crash in software-center when starting service com.ubuntu.sso
Clarifying dobey's response. dobey represents Ubuntu (Canonical), but I do not, so I could be wrong. Canonical does not always offer support if you have installed software using other than Ubuntu Software Center (or an equivalent, just as command line apt-get.) For example, if you are a 'developer' and download source code from a website and build and install it yourself. (Let's call that an unsupported install.) If Ubuntu Software Center does not start, it is likely you have unsupported installed for example: python, zope, sip, PyQt, or other. Ubuntu Software Center is an app written in Python that seems to depend on the example modules. In other words, you have stepped into dependency hell. One strategy for a fix is: undo whatever you unsupported installed last, and reinstall using supported channels . Another strategy is: upgrade your Ubuntu version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085425 Title: Crash in software-center when starting service com.ubuntu.sso To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1085425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 375982] Re: output wrong, uses sky instead of matching texture
The original author Paul Harrison has agreed that I am maintaining resynthesizer now. (And I fixed the reported bug years ago.) However, I believe there is no Debian maintainer now. Thus the package is no longer in Debian or Ubuntu distributions? ( I didn't check.) I myself am not the Debian maintainer, and I'm not ready to commit to it. The latest version (v2.0) is at github.com/bootchk/resynthesizer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/375982 Title: output wrong, uses sky instead of matching texture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp-resynthesizer/+bug/375982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
OK plain and raw events are sent when window belonging to "xinput test- xi2" has the cursor in it, or is in front ( or something like that.) When the second finger is moved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
I upgraded to 12.04, downloaded Qt SDK, built the fingerpaint demo, futzed with xorg.conf.d to get it to load the synaptics Xorg input driver instead of the wacom xorg input driver, futzed with xinput set- prop, etc. to change the settings of the driver. No, the fingerpaint demo doesn't work. I found that "xinput test-xi2 10" ( documented in xinput man page) will display the events from my device. It shows RawTouchUpdate events etc., but apparently no plain TouchEvents ?? when a second finger is moved. The first finger seems to send just plain Motion events?? I futzed some more (with synaptics input driver properties, and also running the demo) and saw some plain TouchBegin etc events, but don't know the conditions needed to reproduce it. So I will search for the difference between raw and plain touch events, and which flavor Qt needs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
Have you thought of using xscope? from http://cgit.freedesktop.org/xorg/app/xscope It would snoop on the net traffic between the X server (including the Xorg driver say synaptics or evdev) and the X client (say Qt and app.) Possibly the xscope tool is not up to date with XI2 protocol packets, but if not, maybe it would dump them in a raw format without interpreting them in the log. A binary strategy: if you see touch events between the two, suspect Xclient (Qt and whatever touch support Ubuntu added), otherwise suspect X server the driver. You could also snoop between X server and Compiz/uTouch which is also X client. Again, maybe uTouch is improperly grabbing. Also, check the commits to they Synaptics Xorg driver. It seems active. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
Erno, You're might be right that there still is a problem somewhere. Unless Unity as window manager X client is grabbing the Xorg.input touch device, and if Qt is built to find the device and become another X-windows client of the Xorg input device, there is no reason it shouldn't get touch events regardless of the count of fingers? But the fault could be in the way I have been testing it. I probably need to read the code, and debug it on my own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
Chase wrote> "You have to put five or more fingers down on a trackpad to start sending events that aren't caught by Unity or X synaptics." My understanding now: Unity is a window manager (more or less.) It is also in the so-called stack that processes touch events. It does gesture recognition and hides touch events from an application (possibly converting sequences of touch events, i.e. gestures, to other event types) unless five touches are used. Is there any way to disable unity gesture recognition (so that all touch events go to the application), similarly to the way you can disable gesture recognition in the synaptics Xorg input driver? The stack: kernel device driver (e.g. wacom) > Xorg input driver (e.g. synaptics) > window manager (e.g. unity) > GUI toolkit (e.g. Qt) > application Shouldn't there be a set of protocols for querying and disabling gesture recognition throughout the entire stack? An API in the GUI TK that an app uses to configure touch? I suppose that is what you architecting now. I understand it is not easy to do, in terms of coordinating all the software pieces and also in terms of providing a consistent user interface across platforms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
Chase, Thanks. How I interpret your last comment is: it is in Ubuntu but not upstream to Qt (whoever that is now, Nokia or other.) As long as I use Ubuntu's version of Qt (whether the source or libraries) it should work. Also, referring to: https://wiki.ubuntu.com/Multitouch , specifically where it says "2 finger gestures require extra setup". I interpret that to mean: without the setup, the synaptics driver (which is inappropriately named, is really THE driver for most touch HID's, not just those of the Synaptics brand) will hide all one finger and two finger events from further up the stack, i.e. from a Qt application? Possibly that is the problem with my testing. The whole business of the stack confuses me. My understanding is a driver can translate certain sequences of touch events into single "mouse" events, i.e. recognize multi-finger gestures, in an attempt to be "friendly" to an app. For example, two finger tap in a certain corner translates to something, as you can see in the System Settings panel for a touchpad. For example, the way you must write an app to be "pen-friendly" is to rely on the translated mouse events instead of raw pen events. How does an application control what the driver does, if the application wants raw touch events to do its own gesture recognition? E.g. using Qt custom QGestureRecognizer. Does Qt have any way of knowing that certain "friendly" mouse events were in fact a sequence of touch events translated by a driver? (Not that it needs to, what could Qt or an app do differently if it knew, besides tell the user that the driver might be improperly "setup" for the gestures that Qt or the app was ready to recognize.) Does Qt QPanGesture require a certain number of fingers, or even require touch at all? For example, would Qt recognize a pan consisting of "mouse" events that were in fact translated from touch events by a touchpad driver? If there is a better forum for this discussion, please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
According to some sources, multitouch doesn't work on Ubuntu desktop until version Qt5. Only on Windows desktop or some mobile platforms. http://qt-project.org/forums/viewthread/12664 Just to be clear, Chase above is correct, uTouch should work, but its not necessarily part of Qt? uTouch is for the Ubuntu platform. Qt uses other technology on Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901630] Re: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen
I had a similar issue and yes: sudo apt-get remove xserver-xorg-input-wacom changes the behaviour. Previously, Settings>Input Devices>Trackpad showed no devices. Now, it shows my Wacom CTT-460. Also, mtdev-test still fails as above but geisttest seems to show the device working with pinches. (geisview fails because gtk is not installed.) Other sources say that the kernel module named "wacom", a *driver*, is distinct from the *Xorg input driver* named "xserver-xorg-input-wacom." Also, the kernel module named "evdev" is distinct from the Xorg input driver named similarly. I don't understand the difference, but /var/log/dmesg still shows a "wacom" driver being used for my device. I am running kubuntu 12.4b. My best guess it is an architectural issue: client vs server. I recall that Ubuntu is moving multitouch and gesture recognition to the client side (the windowing system and application, more or less) from the server side (Xorg, the X11 server.) IOW the Xorg input driver named evdev passes raw multitouch events on to the client (Qt) instead of interpreting them??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901630 Title: multitouch + qt doesn't work (eg fingerpaint demo) with wacom serial touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/901630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 375982] Re: output wrong, uses sky instead of matching texture
** Attachment added: "Full text of patched script." http://launchpadlibrarian.net/26670601/smart-remove.scm -- output wrong, uses sky instead of matching texture https://bugs.launchpad.net/bugs/375982 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 375982] [NEW] output wrong, uses sky instead of matching texture
Public bug reported: Binary package hint: gimp-resynthesizer Ubuntu 9.04 lkk: This is the text of the email created by reportbug (that didn't get sent): Message-ID: <20090512132847.6194.90484.report...@bootch-desktop> X-Mailer: reportbug 3.48ubuntu1 Date: Tue, 12 May 2009 09:28:47 -0400 Package: gimp-resynthesizer Version: 0.16-1 Severity: important About the bug: The symptoms of the bug are that the plugin substitutes a texture that does NOT match the surroundings of the selection. The bug does not appear for every test case, but is repeatable for a given test case (except that resynthesizer uses a random seed and so the results are not al ways identical.) The bug is more evident in black and white images, where there is less informati on (only 8 bits instead of 24 color bits) for the plugin to find correct matches . The bug is more evident where the image contains much background "sky" and yo u invoke the plugin on a selection in the foreground. The essential part of the bug is in line 59 of the original, where a comment by the original author questions why the original code works and suggests alternati ve code. But the fix entails additional changes elsewhere. -- System Information: Debian Release: 5.0 APT prefers jaunty-updates APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty') Architecture: i386 (i686) Kernel: Linux 2.6.28-11-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gimp-resynthesizer depends on: ii gimp2.6.6-0ubuntu1 The GNU Image Manipulation Program ii libc6 2.9-4ubuntu6 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-5ubuntu4 GCC support library ii libgimp2.0 2.6.6-0ubuntu1 Libraries for the GNU Image Manipu ii libglib2.0-02.20.1-0ubuntu2 The GLib library of C routines ii libgtk2.0-0 2.16.1-0ubuntu2 The GTK+ graphical user interface ii libstdc++6 4.3.3-5ubuntu4 The GNU Standard C++ Library v3 gimp-resynthesizer recommends no packages. gimp-resynthesizer suggests no packages. -- no debconf information lkk: end reportbug email lkk: these are my release notes for the patch (attached.) A fix to the Gimp Filter>Enhance>Smart remove selection... script. Release notes: IMPORTANT: Fixed a bug where strange texture (e.g. sky from the top of the image) instead of surrounding texture was synthesized onto the selection, as reported at the website http://registry.gimp.org/ for the resynthesizer plug-in. MINOR: Changed the menu item to "Filter>Enhance>Heal selection..." from "Smart remove selection..." (Justification: New menu item name is shorter and more descriptive. It doesn't use the Heal tool, but the effect is nearly the same. Note the filename is the same, only the menu item name is changed, and it still requires the separate resynthesizer plug-in.) Changed the pop-up help text. (Justification: more descriptive.) ** Affects: gimp-resynthesizer (Ubuntu) Importance: Undecided Status: New -- output wrong, uses sky instead of matching texture https://bugs.launchpad.net/bugs/375982 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
