I still have the HP 840 G1, currently on 22.04. I’ll keep an eye on the
black screen issue and will report back as soon as it happens again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
After checking again today, I noticed the official PPA has Thunderbird
78.8.1, and the issue is thus fixed. Therefore, this bug can be closed.
** Changed in: thunderbird (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Steps to reproduce:
Set up calendar and tasks with a CalDav server and an old Thunderbird
version (up to ca. December 2020).
Set up a recurring task.
Whenever an instance of the recurring task becomes due, mark it as
completed.
Repeat this for a few
Just had a look at my own settings: I have "Dim display when idle"
unchecked in the AC power tab, checked in the Battery tab. I am still
getting a dark screen every now and then, even though I mostly work on
AC power.
--
You received this bug notification because you are a member of Desktop
@Maik Schulze did that change anything? are you still getting the error?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
Title:
Intermittent black screen on HP EliteBook 840 G1
For the issue in #37, I was able to restore the external display by
undocking and re-docking the laptop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
Title:
Intermittent black
And the issue described in comment#37 is also back. This time, however,
after doing Ctrl+Alt+F1, everything was black (except for the cursor
blinking on the internal display), and I was unable to switch back to
the GUI with Ctrl+Alt+F7; I ended up having to cold boot the system
using the power
The black screen issue reappeared on 18.04 sometime last week, after two
completely trouble-free months, and it is quite frequent again. I
haven’t done and in-depth diagnosis or troubleshooting so far. The
flicker issue hasn’t appeared since I upgraded.
--
You received this bug notification
I upgraded to 18.04 last week. So far none of the screen issues (black
screen or image corruption) has reappeared; I will post an update if
anything comes up.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
Steps to reproduce:
1. Enable the German keyboard layout.
2. Open a text editor of your choice.
3. Press AltGr and + (second key after P), then press a.
4. Press AltGr + Shift and +, then press a.
Expected behavior:
Key acts as a dead key, the key sequences produce ã and
I noticed another issue recently: when the device displays woke up after
a period of inactivity, the picture of the external (!) display was
stretched vertically by a factor of 2, with the bottom half missing. I
took a screenshot, but that looked OK and didn’t reflect what I actually
saw.
Also,
I am referring to package updates, still on 16.04, whatever was made
available on the repos in the last ~24 hours before comment #33. (Is
there an install log which will tell me what was updated when?)
--
You received this bug notification because you are a member of Desktop
Packages, which is
After today’s updates, I am seeing another strange issue: whenever all
displays go out due to inactivity and I touch the keyboard or mouse
again, the internal display starts to flicker. It looks as if the entire
image is shifted by some 25% of its width to one side, then to the other
(with the
Forgot to add, the laptop’s currently docked with an external display on
DisplayPort.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
Title:
Intermittent black screen on HP
18.04 LTS is just around the corner and I will be upgrading soon. Is
there any more information you’d like me to gather while still on 16.04?
Please let me know; otherwise I will post any news on how this behavior
also affects 18.04 once I’ve upgraded and used it for a while.
--
You received
That’s great news! Will the fix still make it into 18.04 LTS?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1419523
Title:
GVFS MTP paths are not stable
Status in gvfs:
Fix Released
And the screen just went black again. I haven’t rebooted since I changed
the settings; I will report if I still experience issues after a reboot,
just to be sure.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
I just set the screen timeout to Never; dimming was already disabled. I
did this only for the AC profile, not the battery profile, as I’m on AC
power most of the time. I’ll report back if the screen goes black again
(or if it doesn’t happen for a while).
--
You received this bug notification
I'm currently working without an external display and without a docking
station/port replicator, and the screen just went black for a couple of
seconds. The system had been running for 1–2 hours at the time.
--
You received this bug notification because you are a member of Desktop
Packages,
Re 1: the issue started to happen after I moved the hard disk to the 840
G1 (from a 6930p), which was around August/September. Updates usually
get installed within a day (unless I have only limited Internet access,
which was not the case when I switched laptops), thus the system should
have been
Well, that didn’t take long: screen just went black again for somewhere
around a second. Let me know if you need further input from me.
BTW: currently working without a dock, with an external screen attached
via DP (which has also experienced the bug before the update)—so the
dock doesn’t make a
Update done. I’ll keep an eye on this and report back if I encounter the
issue again (or do not encounter it for a longer time—being a sporadic
bug, it’s difficult to tell if it’s gone away for good).
--
You received this bug notification because you are a member of Desktop
Packages, which is
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052612/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052611/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052607/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052608/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052614/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052613/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052610/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052606/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052609/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052605/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052597/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052603/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052602/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1715749
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052604/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052601/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052599/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052600/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1715749/+attachment/5052598/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Tags added: apport-collected ubuntu
** Description changed:
Occasionally, the internal laptop display goes black for a few seconds,
then comes back to life. The external display stays on. It looks as if
power management were kicking in by error but affecting only the
PS: Debian apparently added the udev rules in usb-modeswitch-data,
version 20160803-1; see https://launchpad.net/debian/+source/usb-
modeswitch-data/+changelog.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
The HP hs3110 WWAN adapter is not recognized and does not work out of
the box.
The device is a rebranded Huawei MU736 but reports a different VID/PID
pair (03f0:521d). With a few manual steps the device will work.
Add the following two udev rules:
# HP hs3110 (Huawei
Update on behavior: the last few times the internal display went black,
I did not touch the keyboard and mouse at all, and the display came back
after a few seconds. (Tested with the laptop in the port replicator and
an external display connected via the DP port.)
--
You received this bug
Public bug reported:
Occasionally, the internal laptop display goes black for a few seconds,
then comes back to life. The external display stays on. It looks as if
power management were kicking in by error but affecting only the
internal display.
When I’m working with the external display, I
Same on Ubuntu MATE 16.04 (as probably on any flavor).
AFAIK the issue was brought about by changes in the behavior of the Save
button: Earlier LibreOffice versions (such as the one included in 15.10)
would gray out the change button when there were no unsaved changes and
enable it as soon as
Haven't tested the dev release yet but upgraded to Ubuntu MATE 15.04
since, and the issue is still there.
** Changed in: xorg (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
It's still an issue on my system; I'll test the dev release and report
here. Since it's a sporadic issue, please allow some time for testing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=744267
** Bug watch added: GNOME Bug Tracker #744267
https://bugzilla.gnome.org/show_bug.cgi?id=744267
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
I'll take care of that as soon as Bugzilla is back (currently down for a
version upgrade).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1419523
Title:
GVFS MTP paths are not stable
Doing some research, I found the MTP spec at:
https://msdn.microsoft.com/de-de/library/ms867188.aspx
Chapter 5.1.1 DeviceInfo Dataset specifies a Serial Number (5.1.1.14),
which is required to be unique among all devices sharing identical
Model and Device Version fields. Thus every MTP device
Public bug reported:
Every time I unplug my Android phone and reconnect it, its URL changes.
E.g. when it is mounted as mtp://[usb:002,002]/ and I unplug and
recoonect it, it gets a new URL, e.g. mtp://[usb:002,003]/.
This behavior breaks all use cases which depend on a stable path (e.g.
shell
Attached is another screenshot from Eclipse. This one happened after
scrolling. The first four lines of the command_new function body are
missing completely (the second line of that block is empty anyway,
however), the fifth line is clipped. Also note the discoloration of the
first two missing
After taking the screenshot, the Save dialog obstructed the corrupt part
of the window, and after the dialog disappeared the window was rendered
correctly again. Anything that causes a re-render (obstruct and re-raise
window, or select text) will restore proper rendering.
--
You received this
** Package changed: ubuntu = xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1418679
Title:
Multiline text controls occasionally get corrupted on refresh
Status in xorg
Any news yet on when there's going to be an official kernel for Precise
that contains the fix?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/957298
Title:
Mouse is
I've tested the 3.10 kernel from the Ubuntu kernel PPA for some more
time, and haven't had any more issues with mouse responsiveness, so I
guess that's resolved. There's just the issue that I have to manually
re-enable Bluetooth and WiFi on every startup.
--
You received this bug notification
Mouse responsiveness looks OK so far, but there seems to be a regression
concerning WiFi/Bluetooth.
When the system comes up, both are disabled and cannot be enabled using
the hardware switch (touch button above the keyboard on the HP 6930p).
WiFi is reported disabled by hardware switch in Gnome
I've installed the 3.10 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-saucy/
(since I don't like testing on a productive system with non-deb installs
that may be hard to uninstall cleanly). According to version number and
file time, it should contain the fix (please correct me
Works for me too. I've tried
#echo N /sys/module/drm_kms_helper/parameters/poll
manually every time I had the issue, and that would fix it. Now I've
automated the step. Not sure if it has any side effects, though.
--
You received this bug notification because you are a member of Desktop
60 matches
Mail list logo
