Thanks @vanvugt for your analysis and help on this. I will stick with
the solution in bug 2079843.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2066353
Title:
MESA: error: ZINK: failed
Submitting as requested.
** Attachment added: "dpkg -l > packages.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2066353/+attachment/5815990/+files/packages.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu
submitting as requested
** Attachment added: "lspci -k > lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2066353/+attachment/5815989/+files/lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
http
*** This bug is a duplicate of bug 2066353 ***
https://bugs.launchpad.net/bugs/2066353
@vanvugt should I click "this bug affects me" on #2066353 and submit the
requested reports or should I just "bug out" of the discussion at this
point? :)
--
You received this bug notification because you a
@kanschat, legend. I've managed to reproduce all of your steps with the
same results.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/2047256
Title:
Ubuntu 24.04 Some image thumbnails
Public bug reported:
While I am unclear which package update impacted the video drivers
detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers
are no longer shown as an option on NVIDIA GeForce GTX 1050 video card.
I can understand the removal of the nvidia 545 drivers as the curr
Temporary solution:
1. jack@jack:~$ xwininfo
2. Click on the invisible square in right top corner
3. Get the square ID (Window id):
"
> xwininfo: Please select the window about which you
> would like information by clicking the
> mouse in that window.
>
>
Actually, I just checked gnome-online-accounts in the gnome-control-
center under X11 nvidia and it is also broken for the Google login.
Clicking the Google Account under the Online Accounts options, produces
and empty window whereas under Wayland nvidia, the sign in content is
displayed. So
https:
I still see the bug with your build. One correction though. Apparently
my proposed fix of changing...
* debian/control.in: Bump Standards-Version to 4.6.2
is insufficient. It seems that my previous workaround of changing
/usr/share/applications/yelp.desktop to contain...
Exec=env WEBKIT_DISABLE_
FYI, I see that same bug, with no content in the Help application, for
both the 6.5.0-5.5 and 6.5.0-6.6 kernels. Only resorting to the
change...
Exec=env WEBKIT_DISABLE_COMPOSITING_MODE=1 yelp %u
or using Wayland suppresses the bug.
--
You received this bug notification because you are a member
FYI, I am running mantic on a workstation with secure boot enabled for
the second drive containing Windows 11 in case that might have some
impact on the bug. The linux debs that are installed are...
ii linux-base4.5ubuntu9
all
** Attachment added: "yelp nvidia bug.png"
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037773/+attachment/5705507/+files/yelp%20nvidia%20bug.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yelp in Ubuntu.
https://bugs.lau
So I assume the blank windows in the Help application under X11 using
the nvidia drivers on Mantic would be resolved if the yelp package were
rebuilt with...
debian/control.in: Bump Standards-Version to 4.6.2
--
You received this bug notification because you are a member of Desktop
Packages, whi
This behavior is seen for both a dist-upgrade of Ubuntu 23.10 from 23.04
or for a clean install of Ubuntu 23.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/2037633
Title:
Help browse
Public bug reported:
The Help browser in the dock on Mantic produces an empty window without
content when launch under X11 using the nvidia-driver-535
535.104.05-0ubuntu4 video drivers. If I logout and login back in under
Wayland, the Help browser behaves normally and produces the expected
content
Public bug reported:
The current /lib/udev/rules.d/61-gdm.rules has a broken rule for
detecting the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1.
This issue can be seen by adding a file /etc/modprobe.d/nvidia-power-
management.conf containing the line...
options nvidia NVreg_PreserveVi
Public bug reported:
Like the previous proposed 42.0-1ubuntu3 packaging of gdm3, the proposed
42.0-1ubuntu4 prevents Wayland from being used on a X570 UD v1.1
motherboard with 5600X processor and Nvidia GT 1050 graphics card. This
proposed change in the gdm3 should be considered a blocker as it de
Public bug reported:
Like the previous proposed 42.0-1ubuntu3 packaging of gdm3, the proposed
42.0-1ubuntu4 prevents Wayland from being used on a X570 UD v1.1
motherboard with 5600X processor and Nvidia GTX 1050 graphics card. This
proposed change in the gdm3 should be considered a blocker as it d
I can confirm that rebuilding the current 41.1-1build1 cheese packaging
with the offending commit reverted...
https://gitlab.gnome.org/GNOME/cheese/-/commit/58de82b3d463b69f4c0bef75667e47020924e28b.patch
...allows my Logitech C525 webcam to operate properly again.
--
You received this bug noti
Matthew, do you see the same corruption if you boot the same machine
with the Logitech C270 camera under a Fedora 36 Beta live image? It
would be interesting to know if their Fedora cheese 41.1 package doesn't
show the same artifact like it doesn't on my hardware.
--
You received this bug notific
It is very odd that Fedora 36 beta also uses a build of cheese 41.1 with
minimal patching and the apparently the same optimizations yet it
doesn't exhibit this artifact.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
ht
** Attachment added: "screenshot of the rendering artifact in cheese under
22.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577395/+files/Screenshot%20from%202022-04-05%2016-53-06.png
--
You received this bug notification because you are a member of Desktop
Pa
I also can confirm that the warnings...
(cheese:2554): cheese-WARNING **: 16:50:13.024: A lot of buffers are being
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late ():
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be
apport information
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577393/+files/lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1967843
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577392/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs
apport information
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577394/+files/lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1967843
Unlike cheese, 'ST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src !
xvimagesink' displays the webcam image fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1967843
Title:
cheese display
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577390/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1967843/+attachment/5577391/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net
apport information
** Tags added: apport-collected
** Description changed:
The cheese application produces a corrupted display under Ubuntu 22.04
with a Logitech C525 webcam. When started from the command line, cheese
produces repeated warnings of the form...
(cheese:4175): cheese-WAR
Public bug reported:
This one of 103 update package that fail.
Now updating alsa-ucm-conf ..
Installing package(s) with command apt-get -y install alsa-ucm-conf
..
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will b
I've seen the same issue with focal and System76 Stable PPA's
460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text
was corrupted after waking from suspend but it has only occurred once so
far.
--
You received this bug notification because you are a member of Desktop
Packages, w
weisswilly1985 THANK YOU - your workaround is a lifesaver on my rpi4,
Raspberry Pi OS (stock kernel).
Here's my tested script to get it installed locally:
# add a workaround script to rememdy eth0 losing it's IP lease randomly
wget
https://raw.githubusercontent.com/WillyWeiss/Avahi-daemon-withdr
Sorry - mixed my words - as you can see it's failing on an attempt to
retreive the remote *signatures* file, not the manifest file. The
manifest is stored in standard class; the signatures file is stored in
DEEP_ARCHIVE class.
--
You received this bug notification because you are a member of De
My incremental job uses the same parameters as the full, and it fails on
glacier/deep because duplicity tries to pull the remote manifest and
can't retrieve it - here's what I run:
duplicity /mnt/backup/src boto3+s3://BUCKETNAME/FOLDERNAME
--file-prefix-archive archive-$(hostna
me -f)- --file-pre
This is not fixed in 8.14 - glacier and glacier deep mode save the
signature files in glacier/deep storage class, and --s3-use-ia stores
BOTH the manifest and signature files in the IA storage class.
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
That is good news! I've been using the touchscreen as much as possible
since last night and have been unable to reproduce the crash.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1870867
I rebooted and disabled all extensions other than the Built-in ones. I'm
still able to trigger the crash. Output of dpkg -l is attached.
** Attachment added: "dpkgl"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/+attachment/5400654/+files/dpkgl
--
You received this bug notifi
I am still getting this bug with the proposed version. Ubuntu 20.04 on a
Lenovo machine.
I hope I updated correctly, I followed the instructions linked above to
activate the "proposed" repository and installed the package with "sudo
apt install mutter/focal-proposed", then deactivated the "propose
Upgrading to Ubuntu 20.04 fixed the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1884391
Title:
PCI/internal sound card not detected
Status in alsa-driver package in Ubu
Here's what I've tried (that I can remember):
- Reinstalling all the ALSA packages
- Rebooting, turning off the sound devices in the BIOS, letting it boot, then
reboot, turn the sound devices back on, and let it boot
- rm -rf ~/.config/pulseaudio && pulseaudio -k
- sudo alsa force-reload
- Remove
Public bug reported:
My sound card stopped being recognized suddenly today. lspci shows the
card, but alsa and pulseaudio don't see it. I verified that the kernel
modules are installed.
I noticed this today when I logged on and the only audio device was the
dummy device. I tried the various fixes
Public bug reported:
I am using onboard on arch Linux with i3 on a convertible laptop. I
have "Auto-show when editing text" enabled as well as "Auto-show only in
tablet mode". The acpid service is enabled with systemd and works
properly. onboard is started when logging in through "exec --no-
st
Public bug reported:
When updating Ubuntu 20.04 to the current proposed updates with the
accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
session crashes out reproducibly into the the gdm3 greeter. At that
point, when you try to log back in, only the background color is
displayed
I agree with Timo: It'd be great to be able to set font size per
screen! I might actually prefer that to screen scaling :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1
*** This bug is a duplicate of bug 1874567 ***
https://bugs.launchpad.net/bugs/1874567
Setting the orientation of my second monitor in `nvidia-settings` works
correctly (panning and tracking are not enabled).
Here's the output of `xrandr` after rotating my second monitor in
`nvidia-settings`:
*** This bug is a duplicate of bug 1874567 ***
https://bugs.launchpad.net/bugs/1874567
I agree with Chris: This current bug (#1875017) is not a duplicate of
bug #1874567 :)
Since updating from 19.10 to 20.20, I'm getting the same issue as Chris:
I have two monitors, both connected to an Nvi
This bug doesn't exist on the same hardware (a 2008 MacPro with Mac
ROM'd GTX680) under current Ubuntu 19.10 with the nvidia-340 package
installed. In that case, booting the default 5.3.0-46-generic kernel in
single user mode produces the expected prompt.
--
You received this bug notification bec
Public bug reported:
Steps to reproduce this bug...
1) Install the current nvidia-340 340.108-0ubuntu2 package.
2) Reboot to confirm nvidia graphics drivers are functional.
3) Reboot and edit the default kernel options to have 'single' before 'quiet
splash'
4) Boot the edited kernel options
The
Public bug reported:
Currently the Nvidia driver packages break the autologin feature of gdm3
whenever the 'splash' option is present on GRUB_CMDLINE_LINUX_DEFAULT in
/etc/config/grub.
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801
This breakage can be avoided by removing '
Couldn't the nvidia packages all be modified to prune 'splash' from
/boot/grub/grub.cfg prior to rebuilding its kernel modules and thus
regenerating the initrd.img files?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ub
This bug is definitely triggered by the built kernel image loading the
nvidia drivers. The autologin failures and associated hangs on restarts
can be suppressed as follows...
1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT
2) Regenerate /boot/grub/grub.cfg with 'sudo up
Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf
under 20.04 has no impact on the autologin bug with nvidia-340.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs
20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro
3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is
shown instead. While the login works fine at the point, restarting then
causes the system to hang rather than completing the restart.
--
You received this
I can also confirm that the nvidia-340 package in 20.04 builds usable
kernel modules and works fine on the same 2008 MacPro with Mac rom'd
GTX680.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
http
I can confirm, on a 2008 MacPro with Apple ROMed GTX680, that the nvidia
440 drivers bundled with the 20.04 beta release show the same behavior.
The Apple Cinema HD display LED comes on (indicating that the driver
loses contact with the display) as nvidia drivers are loaded and nvidia-
modeset exec
** Summary changed:
- nvidia-340 installation issues need to be resolved and the package marked as
'tested'
+ nvidia-440 installation issues need to be resolved and the package marked as
'tested'
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
apport information
** Attachment added: "Profile3Prefs.txt"
https://bugs.launchpad.net/bugs/1852645/+attachment/5307729/+files/Profile3Prefs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1852645/+attachment/5307727/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bug
apport information
** Attachment added: "HookError_source_firefox.txt"
https://bugs.launchpad.net/bugs/1852645/+attachment/5307726/+files/HookError_source_firefox.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
apport information
** Tags added: apport-collected eoan
** Description changed:
I initially posted this bug to the Firefox issue tracker here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined
it was specific to the Ubuntu package.
When I play the video in this J
Very strangely, I can no longer reproduce this bug either.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1852645
Title:
WebAudio API does not behave as expected (Cannot mute videos)
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1852645/+attachment/5307728/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
I initially posted this bug to the Firefox issue tracker here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we determined
it was specific to the Ubuntu package.
When I play the video in this JSFiddle: https://jsfiddle.net/ea9h3bg7/,
there should be no audio. This
Public bug reported:
When my laptop is on its dock there is an option to select which monitor
has the application dock. Selecting my external monitor moves the dock
to my laptop's built in display and selecting built-in display moves the
dock to my external monitor.
Description:Ubuntu Eoan E
Public bug reported:
I have dual-booted Ubuntu and Windows and I don't have sound at all.
Before when restart laptop sound back shortly but if I boot it again
there is no sound anymore. Interesting, when type alsamixer I get cannot
open mixer: No such file or directory. I'm noticing that I have
in
I have this too, but with Slack and Nautilus. Steps to reproduce:
1. Have someone send you a file on Slack.
2. Download the file and click on "Open containing folder".
3. The opened Nautilus window is now grouped with the Slack icon on the
launcher.
--
You received this bug notification because
I am getting the same issue with my Mozilla Firefox browser when I
edited to a captive portal then my Mozilla Firefox 40 is displaying an
error message that is “non-override able security error “, please guide
me to resolve this issue. Once, I couldn’t set up my Mozilla Firefox
then I have resolved
Follow these steps:-
Enter the Press button for SLEEP keyboard shortcut.
Then, Press a standard key on your keyboard and move the mouse.
Now, immediately press the power button on the system and also remember your
Bluetooth devices should be on “off” mode. If still, you cannot resolve this
issue
I believe that I have identified why the newer nvidia drivers which
depend on the new nvidia_drm kernel module fail on Mac hardware. That
new module depends on the ipmi modules. On Mac hardware, unsurprisingly,
the ipmi_si module fails to load and the ipmi device is not created.
Motherboards with i
Public bug reported:
The nvidia-graphics-drivers-340 is essential to many users. For example,
on my MacPro 3,1 equipped with an EVGA GTX-680 Mac version graphic card,
the nvidia 360, 390 and 396 drivers all fail due to issues with the new
nvidia_drm module resulting in no video output on DVI and H
I am seeing the same problem with current cosmic 18.10. The stock
nouveau drivers work fine but using 'sudo ubuntu-drivers autoinstall' to
install either the nvidia-390 or nvidia-396 drivers produces a black
screen (backlighting completely off) after the ubuntu splash screen has
been displayed on r
This was the same issue that was discussed in
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/78584 and it was
fixed in the following versions of Evince, but now it has reappeard (at
least to me)
--
You received this bug notification because you are a member of Desktop
Packages, which is su
Public bug reported:
After upgrading to Ubuntu 18.04 Bionic Evince 3.28.2 shows document
"title" and not document "name" on titlebar. This is very annoying since
titles are pdf metadata that most commonly do not make sense, while pdf
names (i.e. location) are easily modified by user and nexessary
The issue seems to be reappeared (at least to me) in Bionic, with Evince
3.28.2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/78584
Title:
Evince title should be adaptable
Status in
Public bug reported:
error displays on login through xrdp using xfce4 desktop
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architectur
This doesn't create a crash dump for me, and happens without a
suspend/resume/restart
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1738487
Title:
Shell crashes with JS ERROR: Ty
I tried to install package cups-daemon 2.1.3-4 but whenever I clicked
the “install” button then suddenly it stopped working, can you tell me
how I can solve this problem. If someone cannot install safari browser
in Mac then I recommend https://www.appletechnicalsupportnumbers.com
/apple-customer-ca
I endeavored to introduce bundle containers daemon 2.1.3-4 however at
whatever point I tapped the "introduce" catch then all of a sudden it
quit working, would you be able to disclose to me how I can tackle this
issue. In the event that somebody can't introduce safari program in Mac
then I suggest
I tried to install package cups-daemon 2.1.3-4 but whenever I clicked
the “install” button then suddenly it stopped working, can you tell me
how I can solve this problem. If someone cannot install safari browser
in Mac then I recommend www.appletechnicalsupportnumbers.com/apple-
customer-care-numbe
Hi Paul,
Totally understand. I’m on the receiving end of tickets for a living
too😁
Go ahead and close this and thanks for all you do!
Cheers,
Jack Hamm
On Sat, Aug 11, 2018 at 1:35 AM Paul White <747...@bugs.launchpad.net>
wrote:
> Jack,
>
> We are sorry that we do not
Public bug reported:
The nautilus handling of removable media capable of automated insertion
is flawed. On a MacPro 3,1, running bionic for instance, the first use
of the eject key on the keyboard ejects the SuperDrive DVD tray but the
second use of the eject key doesn't cause the tray to auto-ins
Public bug reported:
(First of all, this is my first ever bug report :tada: so some
information may be missing)
Ubuntu Budgie 17.10
gnome-control-center - 1:3.26.2-0ubuntu0.2
Using the `Displays` applet, I am trying to set my primary display to have 200%
scaling.
However, this causes all displa
*** This bug is a duplicate of bug 1724955 ***
https://bugs.launchpad.net/bugs/1724955
** This bug has been marked a duplicate of bug 1724955
unable to drag monitors in Display Arrangement
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
** Attachment added: "GIF of behavior"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1760807/+attachment/5100517/+files/Buggy-Monitor-Rearranging.gif
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-
Public bug reported:
I have a quad monitor setup and I'm unable to rearrange the monitor
layout fully. Two of the monitors are 1680x1050 and the other two are
1920x1080. I can rearrange the monitors in their pairs or resolutions
but cannot rearrange between the two pairs.
ProblemType: Bug
DistroR
this bug seems fixed for me since updating E7470 BIOS to v1.18.5, which
was released 12/22/17 here:
http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=ND42N&lwp=rt
as this leaves us with 0 affected users, I think this bug can be closed.
--
You received this bug notificati
*** This bug is a duplicate of bug 1505409 ***
https://bugs.launchpad.net/bugs/1505409
the exact same is happening to me, also on a latitude e7470, but with
arch linux, 4.14.6 kernel.
I can also reproduce this behaviour including the not-in-reality-existing
monitor showing up in xrandr in Ub
Public bug reported:
Will not come back after screen lock.
The main VAIO laptop lid monitor does not come back, stays dark, no backlight.
I have a second HDMI monitor.
The HDMI monitor will come back from screen lock, but scrambled.
Mouse does not appear.
I have also tried suckless.org slock with
Also on upgrade from 17.04 to 17.10 KDE. In addition, I was running in
a console, as X showed only the mouse cursor, xosview, and otherwise a
black screen. I was hoping to finish the upgrade before troubleshooting
the black screen. Trying the suggestion in comment #7 just got the same
error.
-
With a bit more testing I have one other issue related to the
enhancement -- when I add a secondary monitory and I adjust the scaling
from one of the two options on a 2560x1550 monitor (100% or 200%) the
apply button is not visible anywhere to actually set the setting.
--
You received this bug no
The new implementation does work for updating the settings; however,
it's glitchy.
What I mean by that is when one has the settings set for 200% scaling,
reboots the VM and then logs back in (at least in VMWare -- haven't
tested elsewhere) the scaling for text is at 100%; however, icons appear
to
I can confirm that using X11 as you suggested instead of Wayland is a
viable workaround and that both multi-monitor support and resolution re-
scaling work when moving VMWare Workstation around.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
additional information about when one doesn't hold the package back
(note the error from VMWare Workstation 12.5).
Same thing happens even if the open-vm-tools and open-vm-tools-desktop
are held at 10.1.5.
** Attachment added: "OS updates breaks open-vm-tools-desktop.png"
https://bugs.launchp
Public bug reported:
At first I thought this bug was caused with the recent changes in open-
vm-tools 10.1.10; however, after restoring my VM to the snapshot that
had 17.04 and re-performing the dist-upgrade with open-vm-tools and
open-vm-tools-desktop held at 10.1.5 I am experiencing the same iss
The workaround here is to manually execute
```gsettings set org.gnome.desktop.interface scaling-factor 2```
and then restart the system to be into a scaled (2x) mode.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https
Public bug reported:
When upgrading from ubuntu 17.04 to 17.10 (obviously new window manager)
... there is no longer the ability to configure the HiDPI scaling within
the window manager. This may be an intentional regression or simply
something that got passed by. But I find this configuration opt
*** This bug is a duplicate of bug 1688721 ***
https://bugs.launchpad.net/bugs/1688721
Public bug reported:
The system raised this error message. I don't know why.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24
Alright, attached the different info as requested.
As previously said, only downgrading libldap allowed for libreoffice to
work again... despite how odd it may seem/be. Not sure why, or how
amazed you are, but there we are ;)
Thanks for looking into this, let me know if I can help some more.
--
Output of "dpkg-query -l libreoffice-calc libreoffice-core"
** Attachment added: "dpkq-query"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1697397/+attachment/4895847/+files/dpkq-query
--
You received this bug notification because you are a member of Desktop
Packages, which is sub
1 - 100 of 317 matches
Mail list logo
