Public bug reported:
Ubuntu Desktop 23.10
Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers
network-manager 1.44.2-1ubuntu1.2
When enabling jumbo packets on a wired network device by setting MTU to
9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with
The bug is still present in Ubuntu 32.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2029100
Title:
general protection fault when detaching a gnome-terminal
Status in
-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: erik
@Łukasz: Thanks for the fix. I've tried the packages systemd (and other
packages from the source ball) in version "252.5-2ubuntu3.1".
And the bug went away. Great. Thank you and the other hard-working
people.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Nike - Unfortunately, I don't have the resources to put a new image in
our environment. But I've updated systemd (and all related) libraries to
`252.5-2ubuntu3` and it's still "broken": `systemctl daemon-reexec`
forgets all the old processes and restarts everything.
--
You received this bug
@enr0n: Thanks for your help.
I've deleted my old comment because I messed up the output of the
container.
Here are the outputs of your test script. Output of the host:
hostsystem ~ # bash /tmp/test.sh
cgroupsv1
Output of the container:
container ~ $ bash /tmp/test.sh
hybrid
So, there is a
@enr0n: Thanks for your help.
Here are the outputs of your test script. Output of the host:
hostsystem ~ # bash /tmp/test.sh
cgroupsv1
Output of the container:
container ~ $ bash /tmp/test.sh
cgroupsv2
So, there is a mismatch of the cgroups versions. What does that mean?
I've attached the
Appendix to comment #4: The configuration Ubuntu 20.04 and systemd
245.4-4ubuntu3.20 is working fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2013543
Title:
Clarification: Yes, we've isolated the behavior down to the call of
`system daemon-reexec` from the `/var/lib/dpkg/info/systemd.postinst`
file.
But every call of `system daemon-reexec` will trigger this "bug", if you
have installed the packages in version `249.11-0ubuntu3.4`.
The host machine
** Package changed: sagemath (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2013543
Title:
systemctl daemon-reexec forgets running services
Public bug reported:
See: https://bugs.launchpad.net/bugs/1890177
I am opening a new ticket because I believe there may have been a
regression. I am using rsyslog8.2112.0-2ubuntu2.2 and I still
see this issue.
/etc/rsyslog.d/90-google.conf:
# Google Compute Engine default console
Just want to throw in on a different ARM64 machine I have running Arch,
identical issue. Downgrading to 2.9 worked
pacman -U http://tardis.tiny-
vps.com/aarm/packages/w/wpa_supplicant/wpa_supplicant-2%3A2.9-8-aarch64.pkg.tar.xz
--
You received this bug notification because you are a member of
I found that apple devices and linux devices had no issue with 2.10. My
Androids see it as full signal and say "Saved" underneath it in the WiFi
list but clicking on it does absolutely nothing - no spinning animation,
no change from "saved" to "Connecting", etc. But after about 10 seconds
a
why would you say you won't fix this? it would be easy to implement
systems and policies for ubuntu modders and upstream teams to
coordinate. at minimum, give upstream access to the crash reports,
issue trackers, etc.
it doesn't take manpower, you don't have to test. all you have to do is
i'm in gnome. i open a terminal:
$ ubuntu-bug -w
it types back:
***
After closing this message please click on an application window to
report a problem about it.
Press any key to continue...
after that, i can hit a bunch of keys, click a bunch of things, and nothing
happens. if i
Public bug reported:
I can't hear with headphones, but the speaker does work
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-62-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
The tested snaps indeed use the same libpoppler version as found in
18.04.
I have created a 20.04 boot medium and tested evince using the "try
Ubuntu without installation". This did indeed work, so I stand corrected
that the bug is fixed in current Ubuntu releases.
The evince version in 20.04 is
Since this has not occurred on 18.04 for me, this bug seems to actually
be fixed, with the fix released in 18.04 LTS (ignoring development
versions of Ubuntu).
** Changed in: upower (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
The Debian bug report clearly shows that current unstable still exhibits
the bug.
Since Ubuntu is based on unstable, every Ubuntu version, released or in
development, still exhibits this bug.
As before, the bug is closed as "fixed", but it is not fixed.
The first possible fix in an LTS release
Public bug reported:
I have 2 screens. One horizontally (left) and the other vertically
(right).
Since I updated to Ubuntu 20.04 I can't set the one on the right to
vertical again.
I have tried to install 20.04 in different ways, but the problem
persists.
With the previous version there was no
Public bug reported:
I recently installed Ubuntu 20.04 (20200402) with LVM encryption and automatic
logon.
So I enter my encryption password and after the motherboards boot logo it will
login automatically to desktop. I also chose the additional drivers and so
nvidia-driver-440.
Everything
Hi!
Re-tested with systemd=237-3ubuntu10.39 from proposed (and
libsystemd0=237-3ubuntu10.39), and it works.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Hi!
Tested with systemd=237-3ubuntu10.34 from proposed (and
libsystemd0=237-3ubuntu10.34) and it seems to fix the problem.
What's interesting though, is that a fresh install of bionic came with a
newer version (systemd=237-3ubuntu10.38) - which has the bug. This test
effectively ended up in a
Public bug reported:
I have a 5.1 sound system that is connected via three 3.5 mm audio
cables with my Sound Blaster ZxR: Front Left, Center, Front Right, Rear
Left, Rear Right, LFE
I only get sound from "Front Left"/"Front Right". All other speakers
don't make a sound. I tested Ubuntu 19.04,
The problem has not occured for me on Ubuntu 18.04 yet, it might be
fixed in the latest LTS release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/932133
Title:
upowerd
I would prefer to have a current mawk in Ubuntu, but if that does not
happen, replacing mawk with gawk would be appreciated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mawk in Ubuntu.
This is a silly and very user hostile bug that is still present in
19.10. Seems crazy that it's basically being ignored.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
Yes that's the same issue. And it seems to be fixed in some version as
well? I just tested it on Eoan, using systemd 242-6, and the valid__lft
and preferred_lft did indeed change to 'forever'. Don't know which
version it was fixed in though. Do you think it kan be backported to
Bionic?
The
Repro instructions:
- (Enable systemd-networkd debug logging)
- Start a server with its interface configured with DHCP
- In the netplan config, configure the interface wtih static addressing, using
the exact same address as it already has gotten from DHCP
- Either wait for the initial DHCP lease
@ddstreet It seems to work as expected in Eoan!
netplan.io 0.98-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1836695
Title:
systemd fails to setup static
Hi. I did som further investigation here, and I think I've figured out
what happens in networkd here.
Aug 21 10:54:45 nettest1 systemd-networkd[5463]: ens3: Removing address:
2001:700:1d00:ec00:5054:ff:fe49:4bc9/64 (valid for 4w 2d)
Aug 21 10:54:46 nettest1 systemd-networkd[5463]: ens3: Removing
This continues to happen, more aggressively on 19.04 than on previous
versions. This system popped up with updates today has been running
19.04 the longest of all my systems with "never" as the selected option
and it just keeps checking for updates. I've got two processes seemingly
related, one
Did a PS on one of these systems this morning. Found some shenanigans.
root 3380 1 0 08:25 ?00:00:00 /bin/sh
/usr/lib/apt/apt.systemd.daily install
root 3384 3380 0 08:25 ?00:00:00 /bin/sh
/usr/lib/apt/apt.systemd.daily lock_is_held install
root 3415 3384
In the updates tab, I keep all three boxes checked under "Install
updates from:", because I like to manually run `sudo apt-get update &&
sudo apt-get upgrade` whenever I have a good stable release of software
and feel like stomaching a raft of system changes.
In past versions of ubuntu going back
I should add that if I set "dhcp4: no" explicit when confiugring static
addressing, it behaves as expected, but according to the current
documentation, this parameter should default to "no", so this should not
be neccescary.
--
You received this bug notification because you are a member of
** Summary changed:
- systemd-network fails to apply static IPv4 when the static IP is the same as
previously configured by DHCP
+ systemd-networkd fails to apply static IPv4 when the static IP is the same as
previously configured by DHCP
--
You received this bug notification because you are
Public bug reported:
In bionic, running systemd 237-3ubuntu10.22 and netplan.io
0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an interface
with a static IPv4 address if the statically confiugred address is the
same as the interface already has gotten from DHCP.
This will cause the
Will anything be done here? This basically breaks keepalived for bionic.
I.e, will keepalived >= 2.0.x be available for bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Think it has something to do with the browser used for hotpot
If anyone can find what confi controls in network manager for what browser to
use (suspect chromium because it exhibits same behavior and is default install,
but Firefox works) can find way to change configuration to use working
Public bug reported:
Automatic update to Ubuntu 18.0.4 crash, I don't know why
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-runtime 1.1.8-3.2ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion:
Use Firefox to connect to the hotspot is working for me .. need to find out
how to rejig the Ubuntu hotspot connector to use firefox .. might just be a
browser negotiation issue.
On Sat, Mar 23, 2019 at 10:25 AM fossfellow
wrote:
> I have the same problem on Ubuntu 16.04 LTS
> WiFi works
The problem didn't go away after doing a fresh installation of Ubuntu 18.10.
I have to first disconnect and then connect my Sony MDR-1000x to get the A2DP
profile to work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I think that fixed it.
To add `amdgpu.dc=0`, you must edit your grub configuration
https://askubuntu.com/questions/1029517/amd-rx480-screen-flicker-after-
update-to-18-04#1032198
>To do this, edit the file /etc/default/grub, for example using
>sudoedit /etc/default/grub
>Find the line
Where is that configured?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1799613
Title:
In kernel 4.14.59, monitor resolution is detected correctly. In
kernels after that,
Attached apport
** Attachment added: "apport.xorg._bwf38sg.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+attachment/5205379/+files/apport.xorg._bwf38sg.apport
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
Never had this problem until recently, but seems to align with updates
being installed. Using 18.04.1 and yes, "sudo kbd_mode -s" seems to fix
it. Using Dell XPS 9350.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The problem didn't go away after doing a fresh installation of Ubuntu 18.04.
I have to first disconnect and then connect my Sony MDR-1000x to get the A2DP
profile to work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
After a fresh install of 18.04 Bionic, my USB wireless adapter didn't
show up. Running 'lsusb' provided the device ID for the adapter as
0bda:a811 Realtek Semiconductor Corp. Cross-referencing that ID with
'Ubuntu 18.04' I eventually fell down the rabbit hole at askubuntu.com
and landed here:
Public bug reported:
The message in terminal (hungarian): Az alábbi csomagoknak teljesítetlen
függőségei vannak
depency problem
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libperl5.26 5.26.2-6
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic
i have this 3g modem that works but this not show up in top bar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1758498
Title:
perl crashed with SIGABRT in _dbus_abort()
*** This bug is a duplicate of bug 1756053 ***
https://bugs.launchpad.net/bugs/1756053
Marked this as a duplicate and opened a new bug after finding how to
produce debugging information at
https://wiki.ubuntu.com/X/Troubleshooting.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1756053 ***
https://bugs.launchpad.net/bugs/1756053
Public bug reported:
I upgraded to the 18.04 beta yesterday, which fixed all my problems with
hibernation on my DELL XPS 9350. Most other things have been fine until
ten minutes ago, when I was without
Public bug reported:
I upgraded to the 18.04 beta yesterday, which fixed all my problems with
hibernation on my DELL XPS 9350. Most other things have been fine until
ten minutes ago, when I was without warning thrown out (forcibly logged
out) of my Gnome session.
I was typing away on my keyboard
This also seems to affect ZFS on Linux modules:
zavl: version magic '4.4.0-116-generic SMP mod_unload modversions '
should be '4.4.0-116-generic SMP mod_unload modversions retpoline '
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I have the same problem with the headset Sony MDR-1000X and Ubuntu
17.10. I have to first disconnect and then connect to get the A2DP
profile to work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
I tried to install 'electrum' application by copy and pasting sudo apt-
get install python-qt4 python-pip (in the Terminal Emulator) from
website https://electrum.org/#download.
I had problems with updating ubuntu studio last week. OS will not update
now. I think it was
Public bug reported:
Using afl-fuzz with bmp2tiff the program produced a crash, once the test
case was minimized it produced a segmentation fault with several
commands.
$ lsb_release -rd
Description:Ubuntu 16.04.2 LTS
Release:16.04
$ apt-cache policy libtiff-tools
libtiff-tools:
sudo /usr/share/webmin/changepass.pl /etc/webmin root "your-password" solved it
for me as well
Ubuntu 14.04.5 - Webmin 1.831
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
Uninstalling the whole desktop and reinstalling made this go away. I
guess I had messed something up.
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
After a recent update, Xorg fails to start up, and I get the following
error in journalctl when trying to boot:
---8<---
mars 19 19:18:44 kusma-ubuntu /usr/lib/gdm3/gdm-x-session[1511]: (EE) AIGLX
error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed
*** This bug is a duplicate of bug 1615871 ***
https://bugs.launchpad.net/bugs/1615871
Chiming in to say I experience the same thing, extreme slowdown and
stuttering in chromium but only when a second window is open on a
separate workspace.
uname -a: Linux Latitude-7480 4.8.0-41-generic
systems are
unmounted. If you add the shutdown.target to that rule, systemd somehow
thinks it should be run just before shutdown which is obviously too
late. I'm not sure that is a systemd bug or a systemd feature, but
either way it doesn't do what we want.
Regards,
Erik
--
Erik Mouw
> Op
FWIW, the init script /etc/init.d/unattended-upgrades should be
removed from systemd systems (Xenial, Yaketty).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
,
Erik
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended
I have also tried to let the systemd unit file for this service WantedBy the
umount.target.
According to the systemd documentation that should make it run before the
filesystems
are unmounted, but apparently that doesn't work. systemctl list-dependencies
still shows
that the
Public bug reported:
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in
Public bug reported:
On Ubuntu release: Ubuntu 16.04.1 LTS
Package: debconf-utils
Version: 1.5.58ubuntu1
Arch: amd64
When running (as root):
"debconf-get-selections --installer"
No output is produced. Typically needed to produce a preseed.
** Affects: debconf (Ubuntu)
Importance:
add to grub, radeon.dpm=1, according to this link
https://help.ubuntu.com/community/RadeonDriver#Testing_the_driver
makes flickering slower but it does not stop.
GLX version 1.4 and AMD RV710
I changed grub as xorg used high cpu, when opening abi documents.
--
You received this bug
The proposed packages worked for me on yakkety.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1574324
Title:
pulseaudio crashes when connecting to bluetooth
The problem is solved.
I did nothing.
Maybe an update was the solution
Thxs Christopher
On Sep 29, 2016 06:35, "Launchpad Bug Tracker" <1604...@bugs.launchpad.net>
wrote:
> [Expired for xorg (Ubuntu) because there has been no activity for 60
> days.]
>
> ** Changed in: xorg (Ubuntu)
>
New log attached. This time I was able to get a crash. Pulse didn't
crash with the initial pair, but would still refuse to play audio as
before. However, rebooting the headphones in the presence of the
computer and having them reestablish the pair automatically did cause a
crash. This log has
Attached are two logs with Luke's modified package. I attached two
because I couldn't replicate the bug with the modified logging package.
Instead of immediately crashing and disconnecting after a pair, instead,
the pair would succeed, but audio would not play when set to "High
Fidelity Playback
Public bug reported:
my pc just freezes and i need to reboot a lot of times
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
Private bug reported:
crashes
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ntpdate 1:4.2.8p4+dfsg-3ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10
Uname: Linux 4.2.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Jun 11 07:02:29
I suspect that this was caused by hardware problems.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1538741
Title:
Public bug reported:
I use a Dell Latitude E7440 with an "Dell EURO2 Advanced E-Port II
Docking" docking station.
When docking the laptop into the station, it's impossible to enable the
two screens I have attached to the DVI outputs of the docking station. I
use autorandr, and it reports this:
I suspect that this might be DPMS related. When I use xscreensaver with
screen blanking but no DPMS, the problem doesn't seem to occur. When I
use xscreensaver with DPMS and standby (setting suspend and off to high
values so they don't get triggered), freezes occur when trying to use
the computer
I just had a freeze using 4.0.3 so it's likely that the chance of
occurrence is just too low for me to properly bisect this if it truly is
a kernel problem. If someone knows whether this could be a kernel
problem or if it's likely to be something else, I would appreciate the
information.
--
You
Public bug reported:
After update the system by terminal and executing autoremove, I rebooted
the system and this error appeared
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: linux-image-extra-4.2.0-33-generic (not installed)
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic
The first bad commit seems to be
"[fcfb5aa246c80df8b0a2ccadd7284b4c189149b0] drm: Zero out invalid vblank
timestamp in drm_update_vblank_count."
** Attachment added: "bisectLog.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538741/+attachment/4606394/+files/bisectLog.txt
--
You
** Description changed:
- I've looked at the page at
- https://wiki.ubuntu.com/X/Troubleshooting/Freeze and can reproduce the
- bug at will by entering the command
+ I've got Xorg freezes from time to time. Previously, I was able to
+ reproduce it with
sleep 1; xset s activate
- that's
I'm still bisecting, it's probably either
- fcfb5aa246c80df8b0a2ccadd7284b4c189149b0 (
https://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack/commit/?id=fcfb5aa246c80df8b0a2ccadd7284b4c189149b0
)
or
- 09af0842dac496aae363719c449cb88dcc953299 (
I'm in the process of bisecting.
The latest kernel ( http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.5-rc7-wily/ ) is affected by a freeze, too. I'm not sure
if it's the same as the one that I'm seeing in the 4.0.x series: On the
latest kernel, the system simply freezes after trying to use it
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1921 F pulseaudio
erik 2172 F pulseaudio
Date: Wed Mar 9 15:39:29 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 2
This is a longstanding and huge issue meaning that everyone should just
switch back to Debian instead of using Ubuntu if no one is going to fix
this bug. It is worse now. All mdns, avahi, etc should be removed from
Ubuntu by default and made an OPTIONAL config choice during or after
?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cpio in Ubuntu.
https://bugs.launchpad.net/bugs/1477617
Title:
linux-image-3.13.0-58-generic 3.13.0-58.97 failed to install/upgrade:
run-parts:
X windows still freezes when I haven't used it for some time.
I can't reproduce it by entering a command but the freeze still happens.
The kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.0.4-wily/ definitively has the problem. The latest
kernel (
** Changed in: xorg (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1538741
Title:
Xorg freeze
Status in xorg package in Ubuntu:
Public bug reported:
under upgrade
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 225-1ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Fri Feb 26 21:01:06 2016
itwas under upgrade from 15.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1550502
Title:
package systemd 225-1ubuntu9 failed to install/upgrade: subprocess
Public bug reported:
ATI Radeon 4550
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic i686
.tmp.unity.support.test.1:
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
I can't reproduce this anymore.
** Changed in: xorg (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1538741
Title:
Xorg freeze
After some more testing, it seems that http://kernel.ubuntu.com
/~kernel-ppa/mainline/v4.0.9-wily/ is broken for me, too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
According to my current testing, the last good version is
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.3-wily/ and the first
bad one is http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0.4-wily/ .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I don't know if this is a Kernel problem but I tested a few versions from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D regardless:
- the newest broken version is
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc2-wily/ (that's the newest
version available right now)
- the first
I've upgraded the BIOS to version 2.27 rev 2 from 2011 and upgraded the
kernel.
The problem still occurs with 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22
04:49:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux.
I also tested 3.19.0-43 again and wasn't able to reproduce the problem
with "sleep 1; xset s
According to my notes, the problem also occurred on the following kernels with
Ubuntu 15.10:
- 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64
x86_64 GNU/Linux
- 3.19.0-43-generic #49-Ubuntu SMP Sun Dec 27 19:43:07 UTC 2015 x86_64 x86_64
x86_64 GNU/Linux
--
You
Public bug reported:
I've looked at the page at
https://wiki.ubuntu.com/X/Troubleshooting/Freeze and can reproduce the
bug at will by entering the command
sleep 1; xset s activate
that's mentioned on the page. The freeze occurs when the screen content
reappears after moving the cursor. Cursor
** Attachment added: "dmesg.txt from frozen system, acquired via SSH"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538741/+attachment/4557955/+files/lenovo-t60-freeze-dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Error report popped up at login.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: openssl 1.0.2d-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion:
1 - 100 of 135 matches
Mail list logo
