Ops, apologies for the typo, I'm running Xubuntu 18.04.03
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1801609
Title:
Fails to deactivate dpms off mode after user initiated
I'm running Xubuntu 18.0.03, which hasn't reached end-of-life, and this
bug is still present. It was introduced when I upgraded to kernel 5.0
with xorg 1.20.4-1ubuntu3~18.04.1. It can be circumvented using either
of 2 methods:
1. Uninstalling light-locker and installing xscreensaver
or
2. As
A hypothesis was discussed in bug #1753012 that the root cause of this
bug was in the kernel, specifically in blk-core.c. The patch was finally
merged in kernel version 4.15.0-31-generic. I'm running on
4.15.0-32-generic but the bug is still happening:
1. Xorg starts to become unresponsive: it
I built recode from what I believed to be the upstream source:
https://github.com/rrthomas/recode/
and the bug is not there, although I couldn't pinpoint the specific
commit that fixed it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Public bug reported:
If a filename has 200 or more characters, recode aborts, dumping core.
To reproduce:
1. Generate a filename with 200 characters:
paulo:~/tmp$ file=$(printf 'f%.0s' {1..200})
2. Create a file with this name:
paulo:~/tmp$ echo ã >$file
3. Try to recode this file:
Public bug reported:
gtk3-icon-browser.desktop in package gtk-3-examples references icon gtk3
-icon-browser:
paulo:~$ grep ^Icon /usr/share/applications/gtk3-icon-browser.desktop
Icon=gtk3-icon-browser
but the packages doesn't include it:
paulo:~$ dpkg -L gtk-3-examples | grep
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012
@Alan, oh, you're description of the bug is far more accurate than mine:
it's precisely what I experienced.
I'm running vanilla kernel 4.15.0-23-generic, without your fix, so I
wonder why forcing the intel
This bug is still present in Xubuntu 18.04.
Workaround https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1298578/comments/7 does restore maximum brightness, but not
the actual brightness level before suspending.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012
As I started to suspect of the kernel i915 modesetting driver, yesterday
I put a workaround in place, not sure if it will have any effect. I
created /etc/X11/xorg.conf.d/10-intel.conf:
Section "Device"
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012
I've just got an automated email saying that my bug #1775790 is a
duplicate of bug #1753012, but if I try to open it, I get a not found
page, I suppose because these reports are private to the subscribers.
Dummy me, forgive me: I still had the crash file around, it was just a
question of giving read permission to everyone (since it was only
readable by root and group whoopsie), and running ubuntu-bug over it.
So, after changing problem_types in /etc/apport/crashdb.conf to:
'problem_types':
Thanks for the swift feedback. I had tried to run:
ubuntu-bug /var/crash/FILE.crash
but it complained of lack of permission. I wasn't aware of the
workaround of bug #994921. As soon as I get another crash, I'll follow
your instructions.
--
You received this bug notification because you are a
Public bug reported:
Every night I suspend my laptop and resume it in the morning. At least
once a week, the X server crashes with SIGBUS when resuming from
suspend.
I scoured systemd journals and all logs under /var/log, and this was the
only suspicious message I found:
[ 59358.134] (EE)
Public bug reported:
ExecStop in /lib/systemd/system/transmission-daemon.service is:
ExecStop=/bin/kill -s STOP $MAINPID
when it should be:
ExecStop=/bin/kill -s TERM $MAINPID
since SIGSTOP will just suspend the daemon until it received a SIGCONT.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Public bug reported:
If at-spi2-core is installed, when resuming from suspend messages like
these are logged in systemd journal:
at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily
unavailable) on X server ":0.0"
at-spi-bus-launcher[31720]: after 8065 requests (8065
I'm running Xubuntu 17.10 with gimp 2.8.20 and I still can't open https
URLs with gimp. According to this upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=782319
gimp 2.8 should be able to open https URLs as long as glib-networking is
installed, here I quote that bug report:
> If
In xubuntu 17.10, kdelibs5-data 4.14.34-0ubuntu2, file
/usr/share/mime/packages/kde.xml still includes MIME types all/all and
all/allfiles.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
I have an Epson Stylus TX235W which I used to print and scan wirelessly.
Even after creating the /usr/lib/x86_64-linux-gnu soft links, scanimage
-L still doesn't find my printer through the epkowa backend. However, it
does find it through the epson2 backend, so that I can use xscan or
Simple Scan.
This is fixed in xdg-util's current upstream release 1.1.2+
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1721948
Title:
gvfs-open/xdg-open shows message about 'gio open' which
Public bug reported:
If a filename has an embedded '#', xdg-open fails to open it.
Here's an example. The file:
paulo@monk:~/stage/edit$ ls -l Dino\ vegetariano\ #3\:\ Rúcula\ gum.mp4
-rw-rw-r-- 1 paulo paulo 1822717 Abr 14 00:13 Dino vegetariano #3: Rúcula
gum.mp4
Making sure its MIME type
Public bug reported:
xdg-open is not using the appropriate desktop file to open files with
mimetype image/jpeg. Here's what it should use in my installation:
paulo@monk:~$ xdg-mime query default image/jpeg
geeqie.desktop
and here's the relevant section from
Correcting myself: xdg-open IS using the correct desktop file for
image/jpeg files, but it's getting the command name to exec and ignoring
any other arguments present in the desktop file Exec field.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I've just discovered that xdg-open is not detecting xfce as the desktop,
at this line:
elif xprop -root _DT_SAVE_MODE 2 /dev/null | grep ' = \xfce4\$'
/dev/null 21; then DE=xfce;
As it doesn't detect the desktop, it uses open_generic_xdg_mime() which
indeed picks up only the first word from
23 matches
Mail list logo
