[Bug 2055805] Re: touchpad not working with kernel 6.8
@arighi Yes it's working with 6.8.0-22.22. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
Somehow I can't get 6.8.0-20 after adding the ppa and updating. But in some way I got the 6.8.0-19 kernel now (from proposed?) and that's working fine with the touchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad not working with kernel 6.8
Latest mainline build of kernel 6.8.1 is working. Touchpad on MacbookPro 2012 is working now. Thanks! This kernel is coming to Ubuntu 24.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: touchpad do not working with kernel 6.8
** Summary changed: - tochpad do not working with kernel 6.8 + touchpad do not working with kernel 6.8 ** Summary changed: - touchpad do not working with kernel 6.8 + touchpad not working with kernel 6.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: touchpad not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055805] Re: tochpad do not working with kernel 6.8
Same problem (and solution) for MacBook Pro 2012 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055805 Title: tochpad do not working with kernel 6.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974039] [NEW] OpenOCD segfaults when using stlink with libusb > 1.0.24 (upstream fix available)
Public bug reported: This is an upstream bug that prevents using stlink devices with openocd entirely with the jammy versions of openocd and libusb. This is a bug in openocd that was exposed by a change in libusb-1.0.24. Upstream has committed a fix for this already (intentionally small to facilitate backporting). Please consider backporting this fix into the Ubuntu package. See https://sourceforge.net/p/openocd/tickets/308/ for the bug, and https://review.openocd.org/gitweb?p=openocd.git;a=commitdiff;h=cff0e417da58adef1ceef9a63a99412c2cc87ff3 ** Affects: openocd (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/1974039 Title: OpenOCD segfaults when using stlink with libusb > 1.0.24 (upstream fix available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openocd/+bug/1974039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972985] [NEW] Debouncing not working - wrong clock used
Public bug reported: This is really an upstream bug, but I found no upstream bug tracker or contact address, so I'm hoping the upstream maintainer might be reading along here (and it's a bug in the Ubuntu version as well, so not entirely off here). The problem is that when I set a debounce time on an input pin (with a button attached), that debounce time is not actually applied. If I set a 0.5s timeout, input events are registered immediately (and a lot of them in succession if I press the button a lot of times), instead of only reporting changes when the pin has been stable for 0.5s. To reproduce, I have used the attached program (monitor.c), which is exactly the "monitor GPIO" example from http://abyz.me.uk/lg/examples.html#C%20lgpio with the following line added: lgGpioSetDebounce(h, g, 50); This line sets a bounce time of 500,000 μs (or 0.5 second). When I compile and run it, and press a button attached to gpio 7 a few times quickly, I get: $ gcc -Wall -o monitor monitor.c -llgpio $ ./monitor 7 chip=0 gpio=7 chip=0 gpio=7 level=1 time=116.935984428 chip=0 gpio=7 level=0 time=122.184483056 chip=0 gpio=7 level=1 time=122.311010973 chip=0 gpio=7 level=0 time=122.385752598 chip=0 gpio=7 level=1 time=122.495776931 chip=0 gpio=7 level=0 time=122.536279723 chip=0 gpio=7 level=1 time=122.634267723 ^C Note that the timestamps are a lot less than 500ms apart, which should not be possible if the debouncing was working. I investigated more closely, using the most recent version (downloaded from http://abyz.me.uk/lg/lg.zip a few days ago, I think it's 0.2.0.0) with some debug output added. I found that: - When an event occurs, the timestamp passed by the gpio event is used: https://salsa.debian.org/python-team/packages/lg-gpio/-/blob/upstream/0.2.0.0/lgPthAlerts.c#L488. This timestamp is by default based on CLOCK_MONOTONIC (as documented at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/gpio.h?h=v5.17#n283). - When no event occurs (for 1ms, I think), the `xNowTimestamp` is used. This is returned by `lguTimestamp()` and uses CLOCK_REALTIME (https://salsa.debian.org/python-team/packages/lg-gpio/-/blob/upstream/0.2.0.0/lgUtil.c#L46) - I noticed that both timestamps are really not comparable. IIRC one had about twice as many digits as the other (so I guess one of them is walltime and the other might be time since boot or something). I checked the code and both should be correctly in nanosecond precisions. - The xDebWatEvt compares these two timestamps to decide about bouncing. Since the now timestamp is always bigger than the event timestamps, this effectively disables the debouncing. - If I change `lguTimestamp()` to use CLOCK_MONOTONIC, debouncing works as expected, so all of the code seems to be correct otherwise. I'm not sure if changing `lguTimestamp()` is the right fix here, since it might be used elsewhere that does need CLOCK_REALTIME (I haven't checked closely). The gpio docs (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/uapi/linux/gpio.h#n273) say: * By default the @timestamp_ns is read from %CLOCK_MONOTONIC and is * intended to allow the accurate measurement of the time between events. * It does not provide the wall-clock time. * * If the %GPIO_V2_LINE_FLAG_EVENT_CLOCK_REALTIME flag is set then the * @timestamp_ns is read from %CLOCK_REALTIME. So maybe another fix is to always set the GPIO_V2_LINE_FLAG_EVENT_CLOCK_REALTIME. It seems there is some commented out to set this flag (based on, I think, user-supplied flags) already: https://salsa.debian.org/python-team/packages/lg- gpio/-/blob/upstream/0.2.0.0/lgGpio.c#L244-245 Assuming that debouncing has been tested to work when this code was originally written, I wonder if the default gpio clock was changed at some point, the clock used by lgTimestamp was changed, or maybe this was originally tested on hardware where both clocks are identical? I would dig in a bit deeper, but lacking a version control repo and also changelogs AFAICS, I'm going to just leave this here. I've been testing this on an Orange Pi PC board, running a Ubuntu Jammy- based Armbian image. ** Affects: lg-gpio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "monitor.c" https://bugs.launchpad.net/bugs/1972985/+attachment/5588497/+files/monitor.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972985 Title: Debouncing not working - wrong clock used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lg-gpio/+bug/1972985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
Also, the bug that is described here is about things breaking on *non*-nvidia systems. If you have problems on nvidia systems, please do not add comments here, you are seeing another problem. See also https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/comments/37, and if the bug referenced there does not match your problem, maybe consider opening a new 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/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
@Jack, I'm not sure about nvidia support, but I do think that it is really unrelated to *this* particular bug (which is about a mistake in the rules file that caused the nvidia-specific rules to be applied to other systems, breaking wayland on non-nvidia systems, and which should be fixed now). If you want to discuss wayland support for nvidia systems, maybe it would be good to do this in a separate 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/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
Jeremy, I'm not sure the fix is complete yet, did you test this? I believe our added patch still removes the nvidia-only guard block (leaving only the gdm_nvidia_end label, but no jump to it), so the nvidia suspend checks are still applied to other machines (which will not have e.g. /usr/bin/nvidia-sleep.sh and thus have wayland disabled). I confirmed this by cloning ubuntu3 from salsa, applying your debdiff, applying all quilt patches, manually patching up data/61-gdm.rules.in (@libexec@ -> /usr/libexec) and installing that rules file. With that, I still see the problem - no wayland. If I re-add the guard block (and reboot), I do get a wayland session as expected. I've attached an updated debdiff against ubuntu3 that I succesfully tested with. Note that in addition to the guard block, it also leaves in this comment and run line that I'm not sure is relevant anymore, but I'll leave that for you to judge: # The vendor nvidia driver has multiple modules that need to be loaded before GDM can make an # informed choice on which way to proceed, so force GDM to wait until NVidia's modules are # loaded before starting up. (...) RUN+="/usr/bin/touch /run/udev/gdm-machine-has-vendor-nvidia-driver" ** Patch added: "debdiff-from-working-gdm3_42.0-1ubuntu3-updated-with-guardblock.diff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+attachment/5581062/+files/debdiff-from-working-gdm3_42.0-1ubuntu3-updated-with-guardblock.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
> I have no session menu at all after upgrading to Jammy today. Is this the right bug report for it, or should I open a new one? It wasn't entirely clear to me from the description. Sounds like the same bug - if only one session is available, gdm hides the menu entirely I believe (I also have no menu anymore). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969243 Title: gdm 42.0-1ubuntu4 no longer shows Wayland option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option
I just reported
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969250 which was
marked as duplicate of this bug (which it is), but do check that bug for
a bit more analysis on where the bug is. TL;DR: there are nvidia-
specific checks in 61-gdm.rules that are no longer guarded by a check
for nvidia hardware in the rules file (because the patch reversal in
42.0-1ubuntu4 removed that check).
As a workaround, you can edit /lib/udev/rules.d/61-gdm.rules and
comment out or remove these lines:
## Check if suspend/resume services necessary for working wayland support is
available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_HIBERNATE=`systemctl is-enabled
nvidia-hibernate`'"
ENV{NVIDIA_HIBERNATE}!="enabled", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_RESUME=`systemctl is-enabled
nvidia-resume`'"
ENV{NVIDIA_RESUME}!="enabled", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_SUSPEND=`systemctl is-enabled
nvidia-suspend`'"
ENV{NVIDIA_SUSPEND}!="enabled", GOTO="gdm_disable_wayland"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969250] [NEW] gdm disables wayland for all(?) non-nvidia cards since 42.0-1ubuntu4
Public bug reported:
I was happily using wayland so far on an Intel Tiger Lake laptop. Then I
did an upgrade, including upgrading gdm3 42.0-1ubuntu2 to 42.0-1ubuntu4,
rebooted, and got logged into an Xorg session.
Investigating, it seems this was caused by this patch, reverting in
manually locally fixes things: https://salsa.debian.org/gnome-
team/gdm/-/blob/ubuntu/master/debian/patches/data-Disable-wayland-on-
nvidia-if-suspend-is-broken.patch
Looking at the patch, it seems that the checks introduced by it are
nvidia-specific, but are applied to *all* other cards as well. There
used to be an nvidia-only check wrapping these checeks, but that was
reverted as part of 42.0-1ubuntu4 here: https://salsa.debian.org/gnome-
team/gdm/-/commit/e2f0cca51dd9638c5b2a74a9739539ef4fd427bd
I think this is a pretty urgent and issue. I haven't tested on multiple
machines, but AFAICS this will be unintentionally be disabling wayland
for a lot of people...
I can provide more hardware details, but I think the bug will be obvious
if you look at the resulting 61-gdm.rules file (here's an excerpt,
including some context around the nvidia checks to see they are
unguarded):
LABEL="gdm_pci_device_end"
# disable Wayland if modesetting is disabled
KERNEL!="card[0-9]*", GOTO="gdm_nomodeset_end"
SUBSYSTEM!="drm", GOTO="gdm_nomodeset_end"
IMPORT{parent}="GDM_MACHINE_HAS_VIRTUAL_GPU"
ENV{GDM_MACHINE_HAS_VIRTUAL_GPU}!="1", RUN+="/usr/bin/touch
/run/udev/gdm-machine-has-hardware-gpu"
# but keep it enabled for simple framebuffer drivers
DRIVERS=="simple-framebuffer", GOTO="gdm_nomodeset_end"
IMPORT{cmdline}="nomodeset", GOTO="gdm_disable_wayland"
LABEL="gdm_nomodeset_end"
# Check if suspend/resume services necessary for working wayland support is
available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_HIBERNATE=`systemctl is-enabled
nvidia-hibernate`'"
ENV{NVIDIA_HIBERNATE}!="enabled", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_RESUME=`systemctl is-enabled
nvidia-resume`'"
ENV{NVIDIA_RESUME}!="enabled", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_SUSPEND=`systemctl is-enabled
nvidia-suspend`'"
ENV{NVIDIA_SUSPEND}!="enabled", GOTO="gdm_disable_wayland"
#
# Disable wayland when nvidia modeset is disabled or when drivers are a lower
# version than 470,
# For versions above 470 but lower than 510 prefer Xorg,
# Above 510, prefer Wayland.
KERNEL!="nvidia_drm", GOTO="gdm_nvidia_drm_end"
SUBSYSTEM!="module", GOTO="gdm_nvidia_drm_end"
ACTION!="add", GOTO="gdm_nvidia_drm_end"
# disable wayland if nvidia-drm modeset is not enabled
ATTR{parameters/modeset}!="Y", GOTO="gdm_disable_wayland"
# disable wayland for nvidia drivers versions lower than 470
ATTR{version}=="4[0-6][0-9].*|[0-3][0-9][0-9].*|[0-9][0-9].*|[0-9].*",
GOTO="gdm_disable_wayland"
# For nvidia drivers versions Above 510, keep Wayland by default
ATTR{version}=="[5-9][1-9][0-9].*", GOTO="gdm_end"
# For nvidia drivers versions 470-495, prefer Xorg by default
GOTO="gdm_prefer_xorg"
LABEL="gdm_nvidia_drm_end"
** Affects: gdm3 (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/1969250
Title:
gdm disables wayland for all(?) non-nvidia cards since 42.0-1ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969250/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820586] Re: Should document keys are not trusted by default
Looks good, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820586 Title: Should document keys are not trusted by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1820586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955850] Re: /etc/X11/Xresources no longer loaded, error in patch
Hm, that patch is indeed old, that is not consistent with what I thought was going on. So I looked a little closer. > Looking at the sources, I think this can be traced to: - Switching from a custom Xsession file to the upstream Xsession file in 3.38.0-1ubuntu1, combined with - An oversight in `debian/patches/ubuntu/xresources_is_a_dir.patch` It seems the first point is not actually true. The changelog for that version does list "Don't install debian/Xsession", but it is under "Merge with Debian. Remaining changes:", so it's not a new change in that version, just a statement of an existing difference between Ubuntu and Debian. Looking in the current changelog, the earliest version that mentions this change is 3.26.2.1-2ubuntu1 (from 2017), but already as "remaining". I could not find which version introduced this change, but given the age of the patch, I can imagine it has been around since 2011. In that light, I suspect that the problem I'm seeing is not introduced by switching to upstream Xsession, but by a change in the upstream XSession file that this patch has not been adapted to. And indeed, it's this one: https://gitlab.gnome.org/GNOME/gdm/-/commit/d98debd294060489c77d913d32674c4e08987b8f But indeed, submitting this patch (after fixing it) upstream is probably a good idea to prevent issues like this in the future (but I don't have the time to take that on). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955850 Title: /etc/X11/Xresources no longer loaded, error in patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1955850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955850] Re: /etc/X11/Xresources no longer loaded, error in patch
Just tested, the above test solves the problem 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/1955850 Title: /etc/X11/Xresources no longer loaded, error in patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1955850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955850] [NEW] /etc/X11/Xresources no longer loaded, error in patch
Public bug reported: After upgrading from 21.04 to 21.10, my /etc/X11/Xresources/ directory no longer loads on login. Looking at the sources, I think this can be traced to: - Switching from a custom Xsession file to the upstream Xsession file in 3.38.0-1ubuntu1, combined with - An oversight in `debian/patches/ubuntu/xresources_is_a_dir.patch` Looking at [that patch](https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/debian/patches/ubuntu/xresources_is_a_dir.patch), it has: ```diff --- a/data/Xsession.in +++ b/data/Xsession.in @@ -122,6 +122,13 @@ fi if [ -f "$sysresources" ]; then xrdb -nocpp -merge "$sysresources" +elif [ -d "$sysresources" ]; then +# directory of Xresources files on Debian/Ubuntu +for i in `ls "$sysresources"` ; do +if [ -r "$sysresources/$i" -a -f "$sysresources/$i" ] && expr "$i" : '^[[:alnum:]_-]\+$' > /dev/null; then +xrdb -nocpp -merge "$sysresources/$i" +fi +done fi if [ -f "$userresources" ]; then ``` However, looking a few lines further up in [the original Xsession.in file](https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/data/Xsession.in#L97), I see: ```sh if [ -f /etc/X11/Xresources ]; then sysresources=/etc/X11/Xresources else sysresources=/usr/etc/X11/Xresources fi ``` In other words, if `/etc/X11/Xresources` is a directory, the `sysresources` variable is never set correctly, so the patch should also modify this part of the script. I have observed this broken behavior on version 41~rc-0ubuntu2, but looking at the ubuntu/master branch (as linked above), it still seems broken there. I'm currently testing this patch: ```diff --- Xsession.orig 2021-12-27 22:05:09.038863375 +0100 +++ Xsession2021-12-27 22:05:33.143057433 +0100 @@ -111,7 +111,7 @@ usermodmap="$HOME/.Xmodmap" userxkbmap="$HOME/.Xkbmap" -if [ -f /etc/X11/Xresources ]; then +if [ -e /etc/X11/Xresources ]; then sysresources=/etc/X11/Xresources else sysresources=/usr/etc/X11/Xresources ``` I don't know if it works yet, since I need to log out for that, and close my browser, so need to submit this report first ;-) ``` $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 $ apt-cache policy gdm3 gdm3: Installed: 41~rc-0ubuntu2 Candidate: 41~rc-0ubuntu2 Version table: *** 41~rc-0ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ``` ** Affects: gdm3 (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/1955850 Title: /etc/X11/Xresources no longer loaded, error in patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1955850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901192] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Hi Sebastien (seb128), I do not know which log file you mean. Where in my system can I locate this file? Matthijs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901192 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1901192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901192] [NEW] package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 23 15:30:29 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2012-08-30 (2976 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-23 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901192 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1901192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763006] Re: arm-none-eabi-gdb missed in ubuntu 18.04
I just tried installing gdb-multiarch as a replacement for gdb-arm-none- eabi for an Atmel SAMD target and an STM32 target, and that worked out of the box. Maybe this issue can be closed? A transitional package depending on gdb-multiarch might have been useful, but since this package has been gone for quite some while (also from Debian), I guess that's no longer so relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763006 Title: arm-none-eabi-gdb missed in ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkconfig/+bug/1763006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827741] Re: APT::Default-Release breaks distribution upgrade
This is still a problem: I wanted to upgrade from eoan to focal and forgot about this bug, so the upgrade failed again (I think it actually crashed this time, the GUI window disappeared, but I accidentally dismissed the "send report" prompt, so I'm not sure how exactly). It seems the pattern is still the same: The source.list is rewritten from eoan to focal, Default-Release is unchanged, so subsequent apt operations fail. If I then remove the Default-Release and retry to retry the upgrade with `update-manager -c`, that seems to block indefinitely at some step, even before it offers to upgrade to focal. Reverting the sources.list changes from focal to eoan *and* removing Default-Release does allow the upgrade to be started again (like the last time). I just noticed that when you have insufficient disk space, the upgrade procedure correctly reverts the changes made to sources.list. If this would also happen with a Default-Release-based failure, then at least recovery would be a lot easier (so this is actually a second, separate problem). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827741 Title: APT::Default-Release breaks distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877433] Re: module 'time' has no attribute 'clock'
This is fixed in version (0.5.1-1), which is included in the Groovy 20.10 release. Only Focal 20.04 is still affected, since earlier versions had older versions of Python that did not remove the deprecated module yet. Considering this bug completely prevents this package from working and 20.04 is an LTS, it might make sense to backport this fix. However, since this package is primarily a build-dep for other packages (not used by itself so much) and since there is no backported patch ready to cherry-pick from Debian (In Debian I just updated to a new upstream version), this would need to be cherry-picked from upstream, so I won't be investing the time for that, I think. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877433 Title: module 'time' has no attribute 'clock' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nml/+bug/1877433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884480] [NEW] No error message when upgrade to 20.04 does not work due to outdated packages
Public bug reported: I'm running Ubuntu 19.10 and got a message prompting me to upgrade to 20.04. I clicked the "Upgrade now" (or something similar) button and then nothing happens at all. Looking in the journal, I see: jun 22 08:19:00 grubby check-new-release-gtk[27508]: Checking for a new Ubuntu release jun 22 08:19:00 grubby check-new-release-gtk[27508]: Please install all available updates for your release before upgrading. jun 22 08:19:00 grubby systemd[4266]: update-notifier-release.service: Main process exited, code=exited, status=1/FAILURE jun 22 08:19:00 grubby systemd[4266]: update-notifier-release.service: Failed with result 'exit-code'. jun 22 08:19:00 grubby systemd[4266]: Failed to start Notification regarding a new release of Ubuntu. I suspect this is the reason nothing happens, but that should really be reported to the user graphically, rather than just in the journal. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-59.53-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Mon Jun 22 08:21:57 2020 InstallationDate: Installed on 2019-03-15 (464 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2020-01-30 (143 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884480 Title: No error message when upgrade to 20.04 does not work due to outdated packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1884480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852433] Re: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 3689: invalid start byte
This bug is reported and fixed upstream at https://github.com/SpamExperts/pyzor/issues/74 Looks like the attached patch is essentially the upstream fix. ** Bug watch added: Debian Bug tracker #923077 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923077 ** Also affects: pyzor (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923077 Importance: Unknown Status: Unknown ** Bug watch added: github.com/SpamExperts/pyzor/issues #74 https://github.com/SpamExperts/pyzor/issues/74 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852433 Title: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb7 in position 3689: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyzor/+bug/1852433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832215] Re: If python package is installed under get_python_lib(prefix='/usr/local') it cannot be imported by python
I experience the same problem with python 3.5 on Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832215 Title: If python package is installed under get_python_lib(prefix='/usr/local') it cannot be imported by python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1832215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] Re: Memory leak and incorrect behaviour of generated bindings
I have tested the following versions: Xenial: amd64 4.17+dfsg-1ubuntu0.1 Bionic: amd64 4.19.7+dfsg-1ubuntu0.1 Both distributions are now fixed. For reference, my CI setup: Xenial fixed: https://travis-ci.com/github/MatthijsBurgh/orocos_kinematics_dynamics/jobs/308050115 Bionic fixed: https://travis-ci.com/github/MatthijsBurgh/orocos_kinematics_dynamics/jobs/308050672 Xenial before fix: https://travis-ci.com/github/MatthijsBurgh/orocos_kinematics_dynamics/jobs/307568631 ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] Re: Memory leak and incorrect behaviour of generated bindings
Hi Dmitry, I have tested the updated Xenial package. Still works! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] Re: Memory leak and incorrect behaviour of generated bindings
Hi Dmitry, Please check the attached patch compared to the 4.17 tag. This should provide the solution for 16.04. The diff is in the original mercurial sip repo, https://www.riverbankcomputing.com/hg/sip. But is should be applicable to the git repo. The previous patch missed 2 lines. Therefore the update ** Patch removed: "sip_patch2.txt" https://bugs.launchpad.net/ubuntu/xenial/+source/sip4/+bug/1861601/+attachment/5332696/+files/sip_patch2.txt ** Attachment added: "sip_patch2.txt" https://bugs.launchpad.net/ubuntu/xenial/+source/sip4/+bug/1861601/+attachment/5332707/+files/sip_patch2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] Re: Memory leak and incorrect behaviour of generated bindings
Hi Dmitry, Also the provided test package for 18.04 does fix the problems 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/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] Re: Memory leak and incorrect behaviour of generated bindings
Hi Dmitry, Please check the attached patch compared to the 4.17 tag. This should provide the solution for 16.04. The diff is in the original mercurial sip repo, https://www.riverbankcomputing.com/hg/sip. But is should be applicable to the git repo. ** Attachment added: "sip_patch2.txt" https://bugs.launchpad.net/ubuntu/xenial/+source/sip4/+bug/1861601/+attachment/5332696/+files/sip_patch2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] [NEW] Memory leak and incorrect behaviour of generated bindings
Public bug reported: Happening on all release of sip from 4.16.8 until 4.19.20, so Xenial and newer are all affected. I have tested this on both Xenial(sip 4.17) and Bionic(4.19.7). My request is to update all affected releases to 4.19.21. [Impact] Since the release of sip 4.16.8, but especially commit https://www.riverbankcomputing.com/hg/sip/rev/11a92ebd4840, sip contains two bugs. The code being generated doesn't keep the correct references and a memory leak. The reference problem: (generateVariableGetter in sipgen/gencode.c) In the get function of a class member, there isn't a reference kept to the containing class. Therefore if no other references are kept to the containing class, the containing class in cpp is deleted, also if there are still references to the member. This causes also the member in cpp to be deleted, while in python there is still a reference to the member. Which can't be accessed anymore. Fixed in: https://www.riverbankcomputing.com/hg/sip/rev/137b9be794a1 https://www.riverbankcomputing.com/hg/sip/rev/6a057b2d8537 https://www.riverbankcomputing.com/hg/sip/rev/699facc95914 The memory leak problem: (sip_api_get_reference in siplib/siplib.c) A new reference to "key_obj" is obtained from PyLong_FromLong/PyInt_FromLong. but the reference count is not decreased. Therefore "key_obj" stays alive and produces a memory leak. Fixed in: https://www.riverbankcomputing.com/hg/sip/rev/82ec38dc0e63 Both problems are fixed in 4.19.21. Also the entire changelog between 4.19.20 and 4.19.21 is related to fixing only these two problems. The converstation between me and the develop of sip can be read here: http://python.6.x6.nabble.com/sip-Accessing-members-results-in- incorrect-missing-data-td5266521.html, which might provide some more insight. [Test Case] As sip is a library to generate python bindings. So my test case will be an "applied" test case. My test case is focused on the 'python_orocos_kdl', https://github.com/orocos/orocos_kinematics_dynamics, library. For this test case, please use the "test/sip_bug" branch of my fork of the library, https://github.com/MatthijsBurgh/orocos_kinematics_dynamics. To test the reference problem, follow the steps from travis config. (Of course skipping the installation of python-sip-dev if testing with other sip versions.) To test the memory leak, run the following code (After running the steps from the travis config): ``` import PyKDL as kdl F = kdl.Frame( kdl.Rotation.Quaternion(0, 1, 0, 0), kdl.Vector(1, 2, 3)) while True: v = F.p ``` See http://python.6.x6.nabble.com/sip-Accessing-members-results-in-incorrect-missing-data-tp5266521p5267154.html including plot of the memory usage, http://python.6.x6.nabble.com/file/t383425/mem_leak.png. [Regression Potential] Different versions of SIP have been released on multiple distributions. No bugs have been reported of these versions. I have tested multiple versions of SIP in the affected range on both Xenial and Bionic. I didn't experience any bugs other than the two reported here. [Other Info] Already mentioned, but the conversation between me and the developer, http://python.6.x6.nabble.com/sip-Accessing-members-results-in-incorrect-missing-data-td5266521.html. ** Affects: sip4 (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/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827741] Re: APT::Default-Release breaks distribution upgrade
Just finished the upgrade without problems, so just disabling the default-release temporarily seems to be sufficient. Would be nicer if the upgrade somehow handled this, even if just detecting that it was set and bailing out before rather than during the upgrade and allow the user to unset it manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827741 Title: APT::Default-Release breaks distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827741] Re: APT::Default-Release breaks distribution upgrade
This is still an issue: Just started the disco -> eoan upgrade through the GUI prompt I got, which broke on, I think, the second step (setting up software sources IIRC). A systray icon showed up saying there was a problem with the package manager (saying 'disco', which I have now configured as the default-release, is not a valid distribution). What seems to have happened is the sources.list was updated, replacing disco with eoan sources, breaking because the default-release is no longer available. I tried updating the default-release afterwards, so my system now shows a lot of pending package updates, but I cannot retry the release upgrade since there are pending updates. Instead, I reverted the changes to sources.list (replacing eoan with disco again), removed my default-release, which allowed starting the release upgrade process again and now actually started the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827741 Title: APT::Default-Release breaks distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
I'm also running into this bug (or at least something that looks like it). Typically what happens for me is that I resume from suspend, get an unlock prompt (the system is locked on suspend) and when I log in, the unlock prompt stays visible (the password dots disappear, but I cannot type anything or click any buttons). When I then kill X to recover (ctrl-alt-backspace), I get a new login prompt. Sometimes, logging in again no longer works then, seeing such messages in the console: jun 21 17:01:50 grubby at-spi-bus-launcher[30649]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1024" jun 21 17:01:50 grubby at-spi-bus-launcher[30649]: after 21 requests (21 known processed) with 0 events remaining. jun 21 17:01:50 grubby gsd-power[30703]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-keyboard[30715]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-xsettings[30696]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-media-keys[30731]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby systemd-logind[1100]: Session c9 logged out. Waiting for processes to exit. jun 21 17:01:50 grubby gsd-clipboard[30695]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-color[30713]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gnome-shell[30633]: Connection to xwayland lost >From the messages, I suspect this might be the same problem as the original >poster. However, I'm not entirely sure if at-spi-bus-launcher is actually the culprit here. Could it be that that the xserver or xwayland (I'm not sure which - I'm using the GNOME xorg session since the wayland session doesn't work for me, but the log does talk about xwayland) crashes and that at-spi-bus-launcher is just the first process to find out (because it does so many requests maybe?). I've also seen some instances where at-spi-bus-launcher is not the first one in the log, and I've tried disabling at-spi-bus-launcher by masking it in systemd (not entirely sure if that really worked), but then I also think I saw a crash where at-spi-bus-launcher would not show up in the log at all. One additional observation: At some point during testing, while login would not work, I found a logged in session in some virtual terminal. After logging out that session, logins would work again as normal. I'm not entirely sure if there's a causal relationship there, nor where that logged in session came from (but I was testing with two different users to see if there was something in my homedir that triggered it, so perhaps it came from one of those tests...). Vague, but I wanted to mention this just in case it triggers an idea somewhere :-) As for reporting an upstream issue, that is probably a good idea, though I'm not entirely sure where the cause is. It's probably safe to say it is something in gnome, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827741] [NEW] APT::Default-Release breaks distribution upgrade
Public bug reported:
I just tried to upgrade my Ubuntu system from cosmic to disco, but it
seems the presence of the Default-Release configuration value breaks the
upgrade.
I have some Debian sources in my sources.list so I can occasionally
cherry-pick packages from there. To make sure these are not by default,
I created a /etc/apt/apt.conf.d/10default-release file containing:
APT::Default-Release "cosmic";
When doing the actual upgrade (through `update-manager -c`, but that
probably started something else in the background), I get the following
output in the terminal:
```
Checking for a new Ubuntu release
[25/498]
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23:
PyGIWarning: Gtk was imported without specifying a version first. Use
gi.require_version('
Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, Gdk
/usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py:33:
PyGIWarning: WebKit2 was imported without specifying a version first. Use
gi.require
_version('WebKit2', '4.0') before import to ensure that the right version gets
loaded.
from gi.repository import WebKit2 as WebKit
authenticate 'disco.tar.gz' against 'disco.tar.gz.gpg'
extracting 'disco.tar.gz'
The AppStream system cache was updated, but some errors were detected, which
might lead to missing metadata. Refer to the verbose log for more information.
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-3aipsq2r/disco", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeMain.py",
line 238, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeController.py",
line 2086, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeController.py",
line 1947, in fullUpgrade
self.openCache(restore_sources_list_on_fail=True)
File
"/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeController.py",
line 215, in openCache
return self._openCache(lock)
File
"/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeController.py",
line 243, in _openCache
lock)
File "/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeCache.py",
line 140, in __init__
apt.Cache.__init__(self, progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 138, in __init__
self.open(progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 198, in open
self._cache = apt_pkg.Cache(progress)
apt_pkg.Error: E:The value 'cosmic' is invalid for APT::Default-Release as such
a release is not available in the sources
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 497, in
add_to_existing
self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 450, in write
block = f.read(1048576)
File "/usr/lib/python3.6/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid
start byte
Original exception was:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-3aipsq2r/disco", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeMain.py",
line 238, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeController.py",
line 2086, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-3aipsq2r/DistUpgrade/DistUpgradeController.py",
line 1947, in fullUpgrade
self.openCache(restore_sources_list_on_fail=True)
File
[Bug 1827741] Re: APT::Default-Release breaks distribution upgrade
After this error, removing the Default-Release config and starting `update-manager -c` again shows a popup "Failed to load the package list". Clicking "ok" shows a spinner that takes some time and then offers a partial upgrade, which looks reasonable (but has not finished yet). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827741 Title: APT::Default-Release breaks distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827740] [NEW] Distribution upgrade (18.10 -> 19.04) silently fails due to available updates
Public bug reported:
I'm trying to upgrade from 18.10 to 19.04 by running `update-manager -c`
as instructed by https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes. After
running it earlier to install pending package updates, I now get a
message saying there is a distribution upgrade available (see attached
screenshot).
However, when I click "Upgrade..." nothing happens. When running
`update-manager -c` from a terminal, I can see that after clicking
"Upgrade..." the following is printed and then the process exits:
```
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.
```
Giving that (AFAICS) this tool is supposed to be a GUI application, it
seems a bug that this message is only shown on stdout and not in the
GUI.
A related problem is that `update-manager -c` does not find any pending
updates before deciding to offer an upgrade but does find them when
actually trying to upgrade, but that's probably because I messed up some
stuff wrt to some ppas and Debian I have installed and apt preferences I
set up, since running `aptitude full-upgrade` shows dependency errors.
Note that this is probably just my own mess I should clean up, so I'm
not intending this to be the subject of this bug report (the lack of a
message is). Still, in the interest of understanding and reproducing,
here's what `aptitude full-upgrade` said:
```
$ sudo aptitude full-upgrade
The following NEW packages will be installed:
kicad-demos{a} libglew2.1{a} libpython3.7{a} libpython3.7-minimal{a}
libpython3.7-stdlib{a} python3-wxgtk4.0{a}
The following packages will be REMOVED:
libglew2.0{u} libwxgtk3.0-0v5{u} python-wxgtk3.0{u} python-wxversion{u}
The following packages will be upgraded:
kicad{b}
1 packages upgraded, 6 newly installed, 4 to remove and 0 not upgraded.
Need to get 32,2 MB/36,0 MB of archives. After unpacking 53,9 MB will be used.
The following packages have unmet dependencies:
kicad-footprints : Conflicts: kicad-common but it is not going to be installed
Conflicts: kicad-common:i386 but it is not going to be
installed
kicad-symbols : Conflicts: kicad-common but it is not going to be installed
Conflicts: kicad-common:i386 but it is not going to be
installed
kicad-libraries : Conflicts: kicad-common but it is not going to be installed
Conflicts: kicad-common:i386 but it is not going to be
installed
kicad : Depends: libc6 (>= 2.29) but 2.28-0ubuntu1 is installed
Conflicts: kicad-common but it is not going to be installed
Conflicts: kicad-common:i386 but it is not going to be installed
kicad-templates : Conflicts: kicad-common but it is not going to be installed
Conflicts: kicad-common:i386 but it is not going to be
installed
kicad-packages3d : Conflicts: kicad-common but it is not going to be installed
Conflicts: kicad-common:i386 but it is not going to be
installed
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) kicad [5.0.2-stable-201811280956+bee76a0~70~ubuntu18.10.1 (now)]
2) kicad-demos [Not Installed]
Upgrade the following packages:
3) libwxgtk3.0-0v5 [3.0.4+dfsg-4 (cosmic, now) -> 3.0.4+dfsg-8 (testing)]
4) python-wxgtk3.0 [3.0.2.0+dfsg-8 (cosmic, now) -> 3.0.2.0+dfsg-8
(testing)]
5) python-wxversion [3.0.2.0+dfsg-8 (cosmic, now) -> 3.0.2.0+dfsg-8
(testing)]
Downgrade the following packages:
6) libglew2.0 [2.0.0-6 (cosmic, now) -> 2.0.0-3+b1 (stable)]
```
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-release-upgrader-core 1:18.10.11.6
ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat May 4 22:23:41 2019
InstallationDate: Installed on 2019-03-15 (50 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic dist-upgrade
** Attachment added: "2019-05-04_22-23.png"
https://bugs.launchpad.net/bugs/1827740/+attachment/5261518/+files/2019-05-04_22-23.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827740
Title:
Distribution upgrade (18.10 -> 19.04) silently fails due to available
updates
To manage notifications about this bug go to:
[Bug 1796607] Re: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_dis
Seems upstream diagnosed and fixed this bug in their master branch two weeks ago, and the fix indeed got included in 3.32 (first in 3.31.92, though it seems to have been omitted from their changelog/NEWS file). Any chance of getting this fix backported into the Ubuntu cosmic package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796607 Title: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820586] [NEW] Should document keys are not trusted by default
Public bug reported: Since version 2017.7ubuntu1, the keys installed by the Ubuntu version of debian-archive-keyring are no longer trusted by default. Coming from Debian, this surprised me, but now I've found the changelog entry, I understand the reasoning. Initially, though, I had expected installing debian-archive-keyring to be sufficient to trust the debian archive keys. When it did not work, I checked the README, which does not help here (in fact, it seems to erronously document that keys *are* placed in trusted.gpg.d). I would suggest improving the README: - Note that this package differs from the Debian version and does not install keys as trusted. - Provide a suggestion (preferably a copy-pastable shell command) on how to make these keys trusted. ** Affects: debian-archive-keyring (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/1820586 Title: Should document keys are not trusted by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1820586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685305] Re: Debian keys should not be trusted by default
AFAICS this is fixed in 2017.7.ubuntu1: debian-archive-keyring (2017.7ubuntu1) bionic; urgency=medium * Do not trust debian archive keys by default, and instead ship those keys in usr/share/keyrings. On Ubuntu, this package is mostly used for validating chroots when debootstrapping Debian using /usr/share/keyrings/debian-archive-keyring.gpg -- Dimitri John Ledkov Tue, 16 Jan 2018 16:52:37 + -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685305 Title: Debian keys should not be trusted by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1685305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801731] Re: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1
I tried to deinstall liggs9 and install libgs9-common as was suggested by Synaptic. I got these errors: (Database wordt ingelezen ... 438138 bestanden en mappen momenteel geïnstalleerd.) Uitpakken van .../libgs9-common_9.25~dfsg+1-0ubuntu0.18.04.2_all.deb wordt voorbereid... dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/srgb.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/ps_cmyk.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/lab.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/ps_gray.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/default_gray.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/ps_rgb.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/gray_to_k.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/sgray.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/default_rgb.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: file '/usr/share/ghostscript/9.25/iccprofiles/default_cmyk.icc' not owned by package 'libgs9-common:all' dpkg-maintscript-helper: error: directory '/usr/share/ghostscript/9.25/iccprofiles' contains files not owned by package libgs9-common:all, cannot switch to symlink dpkg: fout bij verwerken van archief /var/cache/apt/archives/libgs9-common_9.25~dfsg+1-0ubuntu0.18.04.2_all.deb (--unpack): nieuw libgs9-common pakket pre-installation script subproces meldde een fout afsluitstatus 1 Fouten gevonden tijdens verwerken van: /var/cache/apt/archives/libgs9-common_9.25~dfsg+1-0ubuntu0.18.04.2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Een pakket kon niet geïnstalleerd worden. Aan het proberen om te herstellen: I removed the mentioned (just placed) files and did the installation, and it worked again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801731 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1801731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801731] [NEW] package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1
Public bug reported: A week ago I had a problem with viewing EPS-files. (Now again). I posted the following bug-description: https://tex.stackexchange.com/questions/457182/problems-after-installing-ubuntu-18-04-and-eps I tried to reinstall libgs9, without result. There are especially problems with viewing EPS-files again, however the original problem is solved. I tried epstopdf and get: epstopdf myfile.eps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- currentshared .currentglobal epstopdf ($Id: epstopdf.pl 45306 2017-09-14 21:41:37Z karl $) 2.27 !!! Error: Writing to gs failed, error code 255 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Nov 5 14:41:59 2018 ErrorMessage: new libgs9-common package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-10-25 (740 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ghostscript Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-27 (9 days ago) ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801731 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1801731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
Good call, thanks! This turns out to be fixed in the latest mainline kernel. Looking at the git log for the i2c_hid driver, I found this commit which I suspect is the fix for my problem. https://github.com/torvalds/linux/commit/52cf93e63ee672a92f349edc6ddad86ec8808fd8 https://patchwork.kernel.org/patch/10589793/ This fix first appeared in the 4.19-rc4 kernel. I tested 4.19-rc3, which is broken while 4.19-rc4 works, which supports my suspicion. I also tested 4.15.0-37.40 (from bionic proposed), which has this same fix backported and also works. I guess this issue can be closed / marked as fix released, but I'm not sure how exactly, so I'll leave that to others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend
It seems this fix also fixes the touch screen not working (no irq storm) after a suspend on an Acer Aspire Switch 11 (and possibly also other modules). See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792309 Title: Fix I2C touchpanels' interrupt storms after system suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1792309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
I also ran the i2c_hid module with debug enabled (`modprobe i2c_hid
debug=1`), which gives a bit of insight in what commands are sent to the
touch screen. On a suspend, it seems to send a sleep command. On a
resume, it sends a power on command, followed by a reset command (which
is properly acknowledge through an empty interrupt, as suggested by the
kernel sources). After that, no further activity happens for the touch
screen (its interrupt also does not trigger according to
/proc/interrupts).
I wonder if this device perhaps needs another power on command, or needs
to be reconfigured (setting report descriptors?) after a reset? I can't
quite find how to do this manually, so I might need to modify the kernel
module for that. Or perhaps try to sniff the windows driver to see how
that handles resume?
Since this device is autodetected through ACPI, I dumped and decompiled the
system's ACPI tables. The part about this device is here:
Scope (_SB.PCI0.I2C1)
{
Device (TPL4)
{
Name (_HID, "SYNA7508") // _HID: Hardware ID
Name (_CID, "PNP0C50" /* HID Protocol Device (I2C bus) */) //
_CID: Compatible ID
Name (_UID, One) // _UID: Unique ID
Name (_S0W, 0x04) // _S0W: S0 Device Wake State
Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
{
If ((Arg0 == ToUUID ("3cdff6f7-4267-4555-ad05-b30a3d8938de") /*
HID I2C Device */))
{
If ((Arg2 == Zero))
{
If ((Arg1 == One))
{
Return (Buffer (One)
{
0x03
// .
})
}
Else
{
Return (Buffer (One)
{
0x00
// .
})
}
}
If ((Arg2 == One))
{
Return (0x20)
}
}
Else
{
Return (Buffer (One)
{
0x00 // .
})
}
}
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (((SDS1 & 0x0200) == 0x0200))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
{
Name (SBFI, ResourceTemplate ()
{
I2cSerialBusV2 (0x0020, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "\\_SB.PCI0.I2C1",
0x00, ResourceConsumer, , Exclusive,
)
Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive,
,, )
{
0x0022,
}
GpioIo (Exclusive, PullDefault, 0x, 0x,
IoRestrictionInputOnly,
"\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0026
}
})
Return (SBFI) /* \_SB_.PCI0.I2C1.TPL4._CRS.SBFI */
}
}
}
In the last block, it describes the I2c address and interrupt that is
being used (also shown in /proc/interrupts). However, it also describes
some GPIO being relevant, but AFAICS the i2c_hid driver does not handle
any GPIOs, so this GPIO might be ignored (or might be handled by an
upper layer of ACPI). I wonder if this pin might be the subject of a
problem similar to the one fixed by https://marc.info/?l=linux-
gpio=147610677825233=2 (but that fixes the intel pinctrl driver, but
I think there are no pinctrl drivers involved here). I couldn't figure
out how to get the state of a GPIO pin, though (other than exporting it
to sysfs, which did not work, probably because the pin is in use?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796580
Title:
Touchscreen breaks after suspend on Acer Aspire Switch 11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1796580/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
I dug around a bit, and found that the touchscreen can also be fixed by reloading the ic2_hid module. It also works to reinitialize just the hid driver for the touchscreen (rather than reloading the entire module) by running: echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/unbind echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/bind Disabling and re-enabling the device with xinput does *not* work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1796580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
** Description changed: I'm not entirely sure this bug belongs in package xinput, but I'm - following the lead of #1275416, which describes the same symptoms (but - on other hardware, so likely a different underlying problem). + following the lead of + https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which + describes the same symptoms (but on other hardware, so likely a + different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: - Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] Device [1025:0930] + Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1796580/+subscriptions -- ubuntu-bugs mailing list
[Bug 1796580] [NEW] Touchscreen breaks after suspend on Acer Aspire Switch 11
Public bug reported: I'm not entirely sure this bug belongs in package xinput, but I'm following the lead of #1275416, which describes the same symptoms (but on other hardware, so likely a different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1796580/+attachment/5198396/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1796580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731637] Re: New upstream Version
** Changed in: openttd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731637 Title: New upstream Version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openttd/+bug/1731637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722745] Re: Virtualbox service fails to start due to hanging plymouth --ping response
Have the exact same issue on 4.13.0-25-generic since today -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722745 Title: Virtualbox service fails to start due to hanging plymouth --ping response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1722745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731637] Re: New upstream Version
I just uploaded 1.7.1-1 to Debian unstable, so this should migrate to Ubuntu at some point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731637 Title: New upstream Version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openttd/+bug/1731637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731637] Re: New upstream Version
W00ps, seems I (Debian maintainer) missed that release. I'll try to upload a package to Debian somewhere this or the next month. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731637 Title: New upstream Version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openttd/+bug/1731637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730398] [NEW] Document need for env_keep+=SSH_AUTH_SOCK
Public bug reported: I just tried installing the Artful version (0.10.3-1) on a Xenial install, and had some problems making it work. It seems that I needed `Defaults env_keep+=SSH_AUTH_SOCK` (or, actually, I used `Defaults env_keep+=SSH_*`) to let pam-ssh-agent-auth see the SSH agent and connect to it. Perhaps a note about this in the README would be helpful, if this is really always required? Or is this not needed with newer sudo versions (I'm using 1.8.16). On a related note, I had some problems with directory permissions (this Ubuntu install had group- and world-write bits enabled on / and /etc). This is probably not a problem on a default install, but it might be good to mention these restrictions when someone wants to move the key file somewhere else (though a proper error message is logged to auth.log by default, even without debug, so that's at least helpful). ** Affects: pam-ssh-agent-auth (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/1730398 Title: Document need for env_keep+=SSH_AUTH_SOCK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-ssh-agent-auth/+bug/1730398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
Even with the script a shutdown/reboot takes a very long time. Any expectations when a fix will be ready? I hit this all the time on 2 installed servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572321] Re: owncloud network access is disabled
Have you tried Nextcloud? Working flawlessly here on several machines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572321 Title: owncloud network access is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/owncloud-client/+bug/1572321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573959] Re: On-screen text disappears after suspend
** Description changed: After resuming from a suspend, almost all text on screen is not visible. This includes menu items, text in all three boxes (list of folders, list of e-mails, e-mail body) in Thunderbird (with the curious exception of "ffl" in the File menu), top menu in Chromium (but not the menu obtained by pressing the hamburger button), and the menus produced by clicking items in the system tray. Also, the apport dialog had no text except for a few capital letters. + + WORKAROUND / 'FIX' (added on March 9, 2017) + Several people have mentioned upgrading to kernel 4.8 or higher solves the issue. As per #81, you can easily install kernel 4.8 (if you're on Ubuntu 16.04, that is) by running + + sudo apt install linux-generic-hwe-16.04 ADDITIONAL INFORMATION: * initctl restart unity-panel-service restarts the panel, but the text is still missing * suspend and resume does not fix the issue * Logging out fixes the issue * Other affected applications: ** Chromium file select dialog ** Terminal (entire window) ** ttys 1-6 (Ctrl+Alt+F1, etc.) ** Document viewer (menus) ** Software Updater ** Rhythmbox ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc ** ubuntu-bug ** Nautilus ** LibreOffice Calc (spreadsheet text contents) ** Firefox * Unity dash is not affected. * Skype is not affected. * Mousing over a button in a dialog correctly shows the text. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 12:04:57 2016 DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics Controller [14c0:0075] InstallationDate: Installed on 2015-01-21 (457 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Compal VAW70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01T01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Compal dmi.board.version: V1.01T01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: VAW70 dmi.product.version: V1.01T01 dmi.sys.vendor: Compal upstart.unity-panel-service-lockscreen.log: (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Apr 22 09:26:06 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1479 vendor BOE xserver.version: 2:1.18.3-1ubuntu2 ** Description changed: After resuming from a suspend, almost all text on screen is not visible. This includes
[Bug 1405874] Re: firefox plugin-container is using too many CPU cycles
Is there any browser available on Ubuntu which does not have this issue? I experienced this with Chrome and tried Firefox, only to find out it's just as bad (FF 51.01 64bit on Ubuntu 16.04.2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405874 Title: firefox plugin-container is using too many CPU cycles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1405874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615068] Re: only lo interface is available
@Rolf - thanks for mentioning iptraf-ng. It's working fine here on Xenial 64 bit. IMHO in scenarios such as these where a 'mother' package becomes obsolete and is replaced by an '-ng' version, the old package should be shipping with a warning upon installation that it's deprecated and should be replaced with the new version. How else should less-informed mortals (such as the bug reporter and myself) know iptraf-ng even exists? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615068 Title: only lo interface is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/1615068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627970] Re: package smbclient 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: package smbclient is not ready for configuration cannot configure (current status 'half-installed')
Correct, solved after upgrading again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627970 Title: package smbclient 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: package smbclient is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1627970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627970] [NEW] package smbclient 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: package smbclient is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: matje@desktop:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 matje@desktop:~$ apt-cache policy smbclient smbclient: Installed: 2:4.3.9+dfsg-0ubuntu0.16.04.2 Candidate: 2:4.3.9+dfsg-0ubuntu0.16.04.3 Version table: 2:4.3.9+dfsg-0ubuntu0.16.04.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2:4.3.9+dfsg-0ubuntu0.16.04.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.3.8+dfsg-0ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages I expected a clean apt-get update, instead I received the error: dpkg: error processing package smbclient (--configure): package smbclient is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: smbclient ProblemType: Package DistroRelease: Ubuntu 16.04 Package: smbclient 2:4.3.9+dfsg-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: smbclient: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Sep 27 10:21:33 2016 DpkgTerminalLog: dpkg: error processing package smbclient (--configure): package smbclient is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package smbclient is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2014-09-04 (754 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 gvfs 1.28.2-1ubuntu1~16.04.1 SambaClientRegression: Yes SourcePackage: samba Title: package smbclient 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: package smbclient is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to xenial on 2016-08-08 (49 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627970 Title: package smbclient 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: package smbclient is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1627970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558712] Re: Remove morituri from archive or switch to gst1.0
Never mind, the 'fix' is in line with the bug description. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558712 Title: Remove morituri from archive or switch to gst1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/1558712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558712] Re: Remove morituri from archive or switch to gst1.0
So removing a package from the 16.04 repo renders a status 'fix released'? Sounds a little odd to me. Besides, the package from 15.10 (https://launchpad.net/ubuntu/wily/amd64/morituri/0.2.3-1) installs just fine on 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558712 Title: Remove morituri from archive or switch to gst1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/1558712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error
I can confirm #9 as it just happened on my 16.04 system as well. However, mine was a fresh install instead of an update from 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447099 Title: /sbin/upstart:indicator-session-unknown-user-error To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1447099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560896] Re: [16.04 beta] REGRESSION - nm-applet does not show all connections
Yup, problem seems to be solved now. Closing the bug. ** Changed in: network-manager-applet (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560896 Title: [16.04 beta] REGRESSION - nm-applet does not show all connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1560896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573639] Re: ownCloud Client system tray icon integration broken
+1 Working again with proposed package. And great tip, Diego / #19. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573639 Title: ownCloud Client system tray icon integration broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1573639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560896] Re: [16.04 beta] REGRESSION - nm-applet does not show all connections
@Chris Cowan - thanks for pointing this out, added it to the description. ** Summary changed: - [16.04 beta] nm-applet does not show all connections + [16.04 beta] REGRESSION - nm-applet does not show all connections ** Description changed: In version 1.0.10 of network-manager-gnome shipping with the 16.04 beta, the nm-applet only shows limited info of the currently used network connection, instead of all connections which are defined / available. As - such, it's impossible to switch connections manually, rendering the - entire feature useless. + such, it's impossible to switch connections manually (or use VPN!), + rendering the entire feature useless. Steps to reproduce: 1. Click on the nm-applet icon 2. Choose "Edit Connections..." 3. Click "Add" 4. Create a static network configuration (i.e. via Ethernet) Notice that this new connection is listed in the "Network Connections" window. 5. Click 'Close' (and restart your computer if you think this will make a difference) 6. Click on the nm-applet icon again Notice that the newly created connection does *not* show up in the drop-down menu that appears. In 14.04 (and before), this feature works as advertised. - Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 network-manager-gnome: - Installed: 1.0.10-1ubuntu1 - Candidate: 1.0.10-1ubuntu1 - Version table: - *** 1.0.10-1ubuntu1 500 - 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.0.10-1ubuntu1 + Candidate: 1.0.10-1ubuntu1 + Version table: + *** 1.0.10-1ubuntu1 500 + 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560896 Title: [16.04 beta] REGRESSION - nm-applet does not show all connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1560896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560896] [NEW] [16.04 beta] nm-applet does not show all connections
Public bug reported: In version 1.0.10 of network-manager-gnome shipping with the 16.04 beta, the nm-applet only shows limited info of the currently used network connection, instead of all connections which are defined / available. As such, it's impossible to switch connections manually, rendering the entire feature useless. Steps to reproduce: 1. Click on the nm-applet icon 2. Choose "Edit Connections..." 3. Click "Add" 4. Create a static network configuration (i.e. via Ethernet) Notice that this new connection is listed in the "Network Connections" window. 5. Click 'Close' (and restart your computer if you think this will make a difference) 6. Click on the nm-applet icon again Notice that the newly created connection does *not* show up in the drop-down menu that appears. In 14.04 (and before), this feature works as advertised. Description:Ubuntu Xenial Xerus (development branch) Release:16.04 network-manager-gnome: Installed: 1.0.10-1ubuntu1 Candidate: 1.0.10-1ubuntu1 Version table: *** 1.0.10-1ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: network-manager-applet (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/1560896 Title: [16.04 beta] nm-applet does not show all connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1560896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518116] [NEW] package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script retur
Public bug reported: error happened while upgrading from 14.10 to 15.04 using do-release- upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: amd64 Date: Fri Nov 20 00:02:45 2015 DuplicateSignature: package:systemd:208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2015-02-19 (273 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) SourcePackage: systemd Title: package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-11-19 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518116 Title: package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1518116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518116] Re: package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script returne
It seemed that by freak behaviour of systemd my /var/run shm partition was 100% full.. the /var/run/systemd/sessions folder was 1.2Gb and filled /var/run to 100% after a reboot all was ok Matthijs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518116 Title: package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1518116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341628] Re: [needs-packaging]openjdk-8 in 14.04
*** This bug is a duplicate of bug 1368094 *** https://bugs.launchpad.net/bugs/1368094 +1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341628 Title: [needs-packaging]openjdk-8 in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1341628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 748261] Re: perl: warning: Setting locale failed
I concur with Armindo, this is a bug (in the installer?) which has been around for many, many years. Apparently the system fails to do a proper locale-gen at the end of the installation. When installing Ubuntu, I always choose US English as language, time zone The Netherlands, keyboard layout US International (dead keys). This combination of settings *ALWAYS* produces this result: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = en_US:en, LC_ALL = (unset), LC_PAPER = nl_NL.UTF-8, LC_ADDRESS = nl_NL.UTF-8, LC_MONETARY = nl_NL.UTF-8, LC_NUMERIC = nl_NL.UTF-8, LC_TELEPHONE = nl_NL.UTF-8, LC_IDENTIFICATION = nl_NL.UTF-8, LC_MEASUREMENT = nl_NL.UTF-8, LC_TIME = nl_NL.UTF-8, LC_NAME = nl_NL.UTF-8, LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). Running sudo locale-gen nl_NL.UTF-8 solves the issue, so IMHO this locale-gen step should be automatically done during the installation of the system (and if this is done already, it's doing it wrong and should be fixed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/748261 Title: perl: warning: Setting locale failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/748261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469113] Re: Timidity makes garbled noise
Similar observation at my end: It works through pulse to my intel_hda sound card, but fails through pulse to my Terratec Aureon 5.1MKII USB audio device. Perhaps a bug in the USB audio driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469113 Title: Timidity makes garbled noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1469113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469113] Re: Timidity makes garbled noise
I can reproduce this on a Debian Jessie system. Bypassing pulseaudio makes playback work normally: pasuspender -- timidity up_on_the_housetop.mid -o hw:0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469113 Title: Timidity makes garbled noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1469113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910736] Re: Add ignore rule for Arduino to udev blacklist
An ignore should probably be added for Arduino.org devices too (there's
two competing Arduino companies now, don't ask):
ATTRS{idVendor}==2a03, ENV{ID_MM_DEVICE_IGNORE}=1
And, while we are here, perhaps also ignore the Pinoccio Scout (arduino-
like device):
ATTRS{idVendor}==1d50, ATTRS{idProduct}==6051,
ENV{ID_MM_DEVICE_IGNORE}=1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910736
Title:
Add ignore rule for Arduino to udev blacklist
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/910736/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039420] Re: NTP security vulnerability because not using authentication by default
So, any updates on this issue now that it has become clear it can be severely abused? See: https://www.blackhat.com/docs/eu-14/materials/eu-14-Selvi-Bypassing-HTTP-Strict-Transport-Security-wp.pdf At least crank up the importance a bit... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1039420 Title: NTP security vulnerability because not using authentication by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1039420/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1039420] Re: NTP security vulnerability because not using authentication by default
So, any updates on this issue now that it has become clear it can be severely abused? See: https://www.blackhat.com/docs/eu-14/materials/eu-14-Selvi-Bypassing-HTTP-Strict-Transport-Security-wp.pdf At least crank up the importance a bit... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039420 Title: NTP security vulnerability because not using authentication by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1039420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049645] Re: missing option to disable gnome-shell lock screen shield
This was fixed upstream, by allowing opening the shield on any printable character keypress, and entering that character into the password field, so you can just type your password while the shield is still shown / moving away. https://bugzilla.gnome.org/show_bug.cgi?id=686740 According to git, this change was first released in 3.7.92. ** Bug watch added: GNOME Bug Tracker #686740 https://bugzilla.gnome.org/show_bug.cgi?id=686740 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049645 Title: missing option to disable gnome-shell lock screen shield To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1049645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313282] Re: apparmor=DENIED for freshclam (CLAMAV)
The changes to the freshclam AppArmor profile does do the trick. Now freshclam reports (as it should be); Clamd successfully notified about the update. Thanks for the quick fix, Matthijs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1313282 Title: apparmor=DENIED for freshclam (CLAMAV) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1313282/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313282] Re: apparmor=DENIED for freshclam (CLAMAV)
The changes to the freshclam AppArmor profile does do the trick. Now freshclam reports (as it should be); Clamd successfully notified about the update. Thanks for the quick fix, Matthijs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313282 Title: apparmor=DENIED for freshclam (CLAMAV) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1313282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313282] [NEW] apparmor=DENIED for freshclam (CLAMAV)
Public bug reported: Not sure if this is a bug, or by design (but I would like some clarification) I recently upgraded my Ubuntu server to 14.04 LTS and notice some error messages regarding Apparmor and Freshclam. So far I know I didn't had these error message with the previous version (13.10). Syslog reports: kernel: [ 113.304926] type=1400 audit(1398085083.946:37): apparmor=DENIED operation=connect profile=/usr/bin/freshclam name=/run/clamav/clamd.ctl pid=2372 comm=freshclam requested_mask=r denied_mask=r fsuid=110 ouid=110 Freshclam log reports: WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl Any reason why freshclam may not read the clamd.ctl? Of course clamd will detect database update and force reload. But should freshclam not be able to notify clamd? ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor clamav freshclam -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1313282 Title: apparmor=DENIED for freshclam (CLAMAV) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1313282/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313282] [NEW] apparmor=DENIED for freshclam (CLAMAV)
Public bug reported: Not sure if this is a bug, or by design (but I would like some clarification) I recently upgraded my Ubuntu server to 14.04 LTS and notice some error messages regarding Apparmor and Freshclam. So far I know I didn't had these error message with the previous version (13.10). Syslog reports: kernel: [ 113.304926] type=1400 audit(1398085083.946:37): apparmor=DENIED operation=connect profile=/usr/bin/freshclam name=/run/clamav/clamd.ctl pid=2372 comm=freshclam requested_mask=r denied_mask=r fsuid=110 ouid=110 Freshclam log reports: WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl Any reason why freshclam may not read the clamd.ctl? Of course clamd will detect database update and force reload. But should freshclam not be able to notify clamd? ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor clamav freshclam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313282 Title: apparmor=DENIED for freshclam (CLAMAV) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1313282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286077] [NEW] ubiquity crashed while installing Ubuntu
Public bug reported: Using the daily 64 bit image from Feb. 27, 2014, I tried installing Ubuntu today from a USB stick to the secondary partition of my laptop's SSD. Since I needed to install it to the secondary partition, I chose 'custom install'. I selected sda2 as the root partition, chose not to format it as it had already been formatted (with ext4) and I wanted to keep the disk label intact. I then got a warning that I didn't have a swap partition. But since I have 8GB RAM and do not use hibernate, I decided to continue. I selected 'Download updates while installing' and 'Download 3rd party software'. Somewhere along the installation, while I was clicking through the slide show, ubiquity crashed. ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 ubuntu@ubuntu:~$ apt-cache policy ubiquity ubiquity: Installed: 2.17.8 Candidate: 2.17.8 Version table: *** 2.17.8 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.17.8 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CasperVersion: 1.337 Date: Fri Feb 28 11:48:19 2014 InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubiquity-2.17.8 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286077 Title: ubiquity crashed while installing Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1286077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286092] [NEW] ubiquity crashed while installing Ubuntu #2
Public bug reported: My secondary attempt to install Ubuntu Trusty, after the failed first attempt (see bug #1286077) results in the same crash. This time, I did everything the same way, but did not select 'Download updates while installing' and 'Download 3rd party software'. So I guess that rules out that those options cause this crash. See bug #1286077 for all other details. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.17.8 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CasperVersion: 1.337 Date: Fri Feb 28 12:09:07 2014 InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubiquity-2.17.8 ubuntu ** Summary changed: - ubiquity crashed during install + ubiquity crashed while installing Ubuntu #2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286092 Title: ubiquity crashed while installing Ubuntu #2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1286092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252467] Re: /etc/cron.d/awstats: wrong user for cron job
I can confirm this problem and wonder if there is any 'real' solution ?
After upgrading to 13.10 there was no problem, until log rotate.
Previous files had 644 for root:adm, now 640 for root:adm
The cron-job for awstats runs as www-data as mention above.
This cause error message when job runs:
Error while processing /etc/awstats/awstats.conf
Create/Update database for config /etc/awstats/awstats.conf by AWStats
version 7.1.1 (build 1.989)
From data in log file /var/log/apache2/access.log...
Error: Couldn't open server log file /var/log/apache2/access.log : Permission
denied
Setup ('/etc/awstats/awstats.conf' file, web server or permissions) may be
wrong.
Check config file, permissions and AWStats documentation (in 'docs' directory).
$ cat /etc/cron.d/awstats
MAILTO=root
*/10 * * * * www-data [ -x /usr/share/awstats/tools/update.sh ]
/usr/share/awstats/tools/update.sh
# Generate static reports:
10 03 * * * www-data [ -x /usr/share/awstats/tools/buildstatic.sh ]
/usr/share/awstats/tools/buildstatic.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awstats in Ubuntu.
https://bugs.launchpad.net/bugs/1252467
Title:
/etc/cron.d/awstats: wrong user for cron job
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1252467/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1252467] Re: /etc/cron.d/awstats: wrong user for cron job
Problem seems a change in new dist logrotate for Apache2 (/etc/logrotate.d/apache2): I change this line: create 640 root adm Into: create 644 root adm As this was the default in my previous version of /etc/logrotate.d/apache2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1252467 Title: /etc/cron.d/awstats: wrong user for cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1252467/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1252467] Re: /etc/cron.d/awstats: wrong user for cron job
I can confirm this problem and wonder if there is any 'real' solution ?
After upgrading to 13.10 there was no problem, until log rotate.
Previous files had 644 for root:adm, now 640 for root:adm
The cron-job for awstats runs as www-data as mention above.
This cause error message when job runs:
Error while processing /etc/awstats/awstats.conf
Create/Update database for config /etc/awstats/awstats.conf by AWStats
version 7.1.1 (build 1.989)
From data in log file /var/log/apache2/access.log...
Error: Couldn't open server log file /var/log/apache2/access.log : Permission
denied
Setup ('/etc/awstats/awstats.conf' file, web server or permissions) may be
wrong.
Check config file, permissions and AWStats documentation (in 'docs' directory).
$ cat /etc/cron.d/awstats
MAILTO=root
*/10 * * * * www-data [ -x /usr/share/awstats/tools/update.sh ]
/usr/share/awstats/tools/update.sh
# Generate static reports:
10 03 * * * www-data [ -x /usr/share/awstats/tools/buildstatic.sh ]
/usr/share/awstats/tools/buildstatic.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252467
Title:
/etc/cron.d/awstats: wrong user for cron job
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1252467/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252467] Re: /etc/cron.d/awstats: wrong user for cron job
Problem seems a change in new dist logrotate for Apache2 (/etc/logrotate.d/apache2): I change this line: create 640 root adm Into: create 644 root adm As this was the default in my previous version of /etc/logrotate.d/apache2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252467 Title: /etc/cron.d/awstats: wrong user for cron job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1252467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892706] Re: after gdm login, keyboard doesn't send KeyPress events
In case any one else comes across this problem: I had exactly the same symptoms and found out they were caused by xbindkeys that was started in the background. Removing my .xbindkeysrc solved the problem 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/892706 Title: after gdm login, keyboard doesn't send KeyPress events To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/892706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically
So I understand this bug has been fixed upstream over 5 months ago. Now how long will it take for this fix to trickle down into Precise? Anything I can do to speed it up? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/280571 Title: NetworkManager does not auto-connect to VPNs marked Connect Automatically To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/280571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263455] [NEW] Desktop not mirrored with Samsung hdmi dock
Public bug reported: I asked the following as a question and was suggested to report it as a bug, so here it goes: I am using ubuntu touch on my galaxy nexus, together with the 'official' samsung HDMI dock. However, when docked, the screen is not mirrored to my hdmi display. My research got me to the following information on this: Apparently the stock android kernel has a setting for this particular hdmi device which allows it only to show video (and not even subtitles). This has been fixed by a minor kernel mod as described here: http://forum.xda-developers.com/showthread.php?t=1780481 Could this mod be included in the linux-maguro kernel as well? adb getprop result: maguro root@ubuntu-phablet:/# lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 root@ubuntu-phablet:/# apt-cache policy linux-maguro linux-maguro: Installed: (none) Candidate: 3.0.0.3.5 Version table: 3.0.0.3.5 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty/universe armhf Packages ** Affects: linux-maguro (Ubuntu) Importance: Undecided Status: New ** Attachment added: media info file of the device https://bugs.launchpad.net/bugs/1263455/+attachment/3934086/+files/media-info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263455 Title: Desktop not mirrored with Samsung hdmi dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-maguro/+bug/1263455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184691] Re: nvidia kernel module fails to build with kernel 3.10 or later [In function ‘nv_i2c_del_adapter’:... error: void value not ignored as it ought to be]
I'm confused. I just got this error while trying to installing linux- generic-lts-saucy on my 12.04.3 machine. The build for both nvidia-304 and nvidia-319 failed: nvidia-304 304.88-0ubuntu0.0.3: nvidia-304 kernel module failed to build nvidia-319 319.32-0ubuntu0.0.1: nvidia-319 kernel module failed to build While I understand the build failing for nvidia-304 (which has status 'Triaged'), I don't see why it would fail for nvidia-319 (which has status 'Fix Released'). I wonder if either: 1. The bug was fixed for nvidia-319-updates instead but nvidia-319 was mistakenly tagged 'Fix Released' 2. The bug has actually not been fixed in nvidia-319 3. I'm experiencing a different bug I will install nvidia-304-updates and nvidia-319-updates to see if that fixes anything (I expect it will only work on 304-updates), anything else I can try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184691 Title: nvidia kernel module fails to build with kernel 3.10 or later [In function ‘nv_i2c_del_adapter’:... error: void value not ignored as it ought to be] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1184691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239299] Re: Launcher, Dash and menus are covered with 'gradients'
Screenshot 3 - Dash active ** Attachment added: Screenshot from 2013-10-13 09:01:47.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+attachment/3876477/+files/Screenshot%20from%202013-10-13%2009%3A01%3A47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239299 Title: Launcher, Dash and menus are covered with 'gradients' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239299] Re: Launcher, Dash and menus are covered with 'gradients'
screenshot 4 ** Attachment added: Screenshot from 2013-10-13 09:03:49.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+attachment/3876478/+files/Screenshot%20from%202013-10-13%2009%3A03%3A49.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239299 Title: Launcher, Dash and menus are covered with 'gradients' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239299] Re: Launcher, Dash and menus are covered with 'gradients'
Screenshot 2 ** Attachment added: Screenshot from 2013-10-13 09:01:31.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+attachment/3876472/+files/Screenshot%20from%202013-10-13%2009%3A01%3A31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239299 Title: Launcher, Dash and menus are covered with 'gradients' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239299] [NEW] Launcher, Dash and menus are covered with 'gradients'
Public bug reported: When running Saucy final beta from a USB stick, the Launcher, Dash and top menu bar are covered with 'gradients'. See the attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CasperVersion: 1.336ubuntu1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 13 09:13:31 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:81f7] LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MachineType: To Be Filled By O.E.M. ALiveNF4G-DVI MarkForUpload: True ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.name: ALiveNF4G-DVI dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/10/2006:svnToBeFilledByO.E.M.:pnALiveNF4G-DVI:pvrToBeFilledByO.E.M.:rvn:rnALiveNF4G-DVI:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALiveNF4G-DVI dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20130920-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Oct 13 08:58:59 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUVC Camera (046d:0802) KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2.901-2ubuntu5 xserver.video_driver: nouveau ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu ** Attachment added: 20131013 saucy final beta compositing problem 01.png https://bugs.launchpad.net/bugs/1239299/+attachment/3876450/+files/20131013%20saucy%20final%20beta%20compositing%20problem%2001.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239299 Title: Launcher, Dash and menus are covered with 'gradients' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239315] [NEW] ubiquity does not display interface
Public bug reported: When running saucy final beta from a USB stick (option Try Ubuntu before installing), ubiquity does not show an interface when started. As a result, Ubuntu cannot be installed. - Double-clicking the icon on the desktop seems to produce no result (nothing happens) - Clicking on the 'Install Ubuntu 13.10' icon in the shortcut bar on the left side has the same result (none) - Running ubiquity gtk_ui from a terminal fails: Ubiquity is already running! - After doing a sudo killal ubiquity and then running ubiquity gtk_ui again, no warnings are displayed, but the ubiquity user interface still does not show. After killing ubiquity again (from another terminal, CTRL+C does not work), the terminal shows the following information: Terminated umount: /var/lib/polkit-1/localauthority/90-mandatory.d: not mounted - Also tried running ubiquity (without gtk_ui) from the terminal - same result (none) - Also tried running sh -c 'ubiquity gtk_ui' from the terminal - same result (none) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.20 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 CasperVersion: 1.336ubuntu1 Date: Sun Oct 13 10:23:25 2013 InstallCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubiquity-2.15.20 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239315 Title: ubiquity does not display interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1239315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168191] Re: OpenTTD 1.3.0 Stable Is Out
Given that raring has been released without 1.3.0, but that 1.3.0 has been (automatically) imported into saucy, I think this bug can be closed. ** Changed in: openttd (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168191 Title: OpenTTD 1.3.0 Stable Is Out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openttd/+bug/1168191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 867917] Re: openttd crashed with SIGABRT in ClientNetworkContentSocketHandler::ReverseLookupDependency()
Given the age of the original report, I'm not sure if it's still worth investigating this. It's likely that this bug has been fixed already in newer OpenTTD versions. If the bug still occurs for you, please reopen this bug or leave a comment. ** Changed in: openttd (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867917 Title: openttd crashed with SIGABRT in ClientNetworkContentSocketHandler::ReverseLookupDependency() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openttd/+bug/867917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170976] Re: Desktop icons changed by user, display white border around them
** Changed in: nautilus (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170976 Title: Desktop icons changed by user, display white border around them To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1170976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1172172] Re: Some multitouch gestures not working on 13.04
On 05/30/2013 12:17 PM, Stefan Skotte wrote: What the heck ? I used the three finger move windows all the time - and I dont really plan to have a touchscreen... Jz... Get this feature back ! LIKE -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:matthijslamb...@jabber.crossmarx.nl Winnaar RADRACE 2006,2007 en 2008: http://www.crossmarx.com/radrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172172 Title: Some multitouch gestures not working on 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1172172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
