** Description changed:
chtmax98090 intel HD audio device doesn't work out of the box after
installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
audio devices.
Audio options shows device and it works if I do this:
- git clone https://github.com/plbossart/UCM.git
- cd
I am running Ubunti 18.04.2 in an Enhanced Hyper-V session -
https://www.zdnet.com/article/windows-10-tip-run-ubuntu-linux-in-an-
enhanced-hyper-v-session/.
I am facing the same problem.
Tried
Switching input method between xim and ibus
Changing theme to Adwaita
Nothing works for me.
Given the
Internal audio is disabled in the BIOS.
--
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/1833652
Title:
[SB-XFi - Creative X-Fi, playback] No sound at all
Status in alsa-driver pac
Public bug reported:
Installed a new X-Fi sound card, but no audio is being heard during
playback on Ubuntu 18.04.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-22-generic
*** This bug is a duplicate of bug 1832000 ***
https://bugs.launchpad.net/bugs/1832000
** This bug has been marked a duplicate of bug 1832000
NVidia fails everytime a new kernel update is released : nvidia-340
340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build
--
You received
Please reproduce the freeze again, then reboot and run:
journalctl -b-1 > prevboot.txt
and send us the file 'prevboot.txt'.
** Tags added: amdgpu
** Summary changed:
- screen freeze after suspend
+ [amdgpu] screen freeze after suspend
** Package changed: xorg (Ubuntu) => xserver-xorg-video
It appears there's only one caller of this function in gnome-shell:
js/ui/osdMonitorLabeler.js:let monitor =
this._monitorManager.get_monitor_for_connector(connector);
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Tracking in:
https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
** Description changed:
+ https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
+
gnome shell crashes when I go to Settings -> Devices -> Displays
ProblemType: Crash
DistroReleas
*** This bug is a duplicate of bug 1833558 ***
https://bugs.launchpad.net/bugs/1833558
** This bug has been marked a duplicate of private bug 1833558
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs
*** This bug is a duplicate of bug 1833527 ***
https://bugs.launchpad.net/bugs/1833527
** This bug has been marked a duplicate of bug 1833527
in gnome settings audio section does not see any sound card
--
You received this bug notification because you are a member of Desktop
Packages, whi
*** This bug is a duplicate of bug 1833558 ***
https://bugs.launchpad.net/bugs/1833558
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.32.1-1ubuntu1~19.04.1, the probl
It's good if you can't reproduce a bug any more. Although your
AlsaInfo.txt shows the main problem was that pulseaudio wasn't running
at all:
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - No
Let us know if you wish to investigate that problem again.
** Changed in: puls
gnome-shell!587 only says it fixes gnome-shell#1325. If you think it
also fixes gnome-shell#1370 then you should probably add a comment here:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/587
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1793640 ***
https://bugs.launchpad.net/bugs/1793640
** This bug has been marked a duplicate of bug 1793640
Pulseaudio fails to detect sound card, while timidity is installed
--
You received this bug notification because you are a member of Desktop
Packag
Actually, maybe those other DMs don't run as root. My memory is failing.
So again maybe we do want a similar workaround in gdm3. But that doesn't
seem to be the root cause of the bug.
** Changed in: gdm3 (Ubuntu)
Status: Invalid => Opinion
** No longer affects: mutter (Ubuntu)
--
You rec
> If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)
I don't understand the question, sorry. The statement "it won't work" is
wrong. Wayland does work. This bug is about Xorg
I think his point was to isolate the problem as being gdm3's wayland code.
If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)
my point was that you marked this as invalid, bu
** Changed in: thunderbird
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1813471
Title:
Thunderbird crashes with GTK_USE_PORTAL environment variab
Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind
of pointless. It's pointless because the most common reason for using
nvidia-drm.modeset=1 is to get Wayland support. I know there are other
reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in
PRIME setups. But
Here are the crash reports generated using the beta
bp-b5718f8c-7977-46a4-84b8-d190b0190618 <-- with 'GTK_USE_PORTAL=0
thunderbird'
bp-0fd780e4-9d38-4b70-b887-208e50190618 <-- with 'GTK_USE_PORTAL=1
thunderbird'
--
You received this bug notification because you are a member of Desktop
Packages,
I've tested 6.70.0, 6.70.1, 68.0b1, and the daily on Ubuntu 19.04, all
crash after all dialogs are closed and it seems (still needs a little
more testing) at least one email account is setup.
Whats odd is that unless you explicitly set GTK_USE_PORTAL = 1 in the
string to launch TB (i.e. 'GTK_USE_
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in wh
Ok, including my own testing we got 4 positive feedback.
With that being said, I have just submitted the patch to our kernel team a few
minutes ago.
This will be part of the next cycle 01-July through 21-July.
Thanks for the pre-SRU testing, we will need you guys one more time
during the testin
"gdm3 compile without wayland", I meant
--
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/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
Status in gdm3 packa
What we know about this bug is that gdm3, nvidia and modeset=1 is broken
under configurations which are not broken when sddm and lightdm are
used.
we know that gdm3 sessions with external monitors work with root
permissions.
we know that gdm3 compiled with wayland also works (according to the
gen
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in wh
Additional confirmation...
Looks like this updated kernel fixes the issue on the affected test VM I
created.
Using the detailed directions in comment #75, I was able to install the
new test kernel and reboot.
Verified the expected version value with uname and then installed the
packages that wer
Public bug reported:
Ubuntu 19.04
Processor Intel® Core™ i5-3337U CPU @ 1.80GHz × 4
Gnome 3.32.1
OS: 64-bit
My speakers are recognized by the system however no sound comes out of them.
This happens wither plugging them to my laptop or to my projector which is
connected via HDMI. This is how it
There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/587
--
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/1831161
Title:
App-switcher icons too
There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/587
--
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/1832792
Title:
App-switcher icons too
** Description changed:
After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes
in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-
- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is
+ plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA ja
Public bug reported:
It's most likely amdgup driver needs an upgrade. Problem occurs since
kernel upgrade to 5.0
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
Uname: Linux 5.0.0-18-generic x86_64
ApportVersion:
Additional confirmation...
Working under VMware Workstation v12.5.7 running kernel 4.15.0.52:
Having performed the workaround of uncommenting the
WaylandEnable=false...
- Re-commented the line & rebooted to experience the hang with the
Ubuntu logo before the login screen
- Using your ppa,
-testing-chromium-browser-deb-to-snap-transition/11179/52?u=paulw2u
The installation of the deb to snap transition (for all major Ubuntu
flavours) was in a live environment using ISOs dated 20190618 or
20190620. This installed Chromium 75.0.3770.80 or 75.0.3770.90
depending on the date of the
Great for the quick feedback.
I have until June 26th to submit the patch for the next cycle[0]
It's giving me a couple of more days to get other impacted users
feedback.
[0] - https://kernel.ubuntu.com/
- Eric
--
You received this bug notification because you are a member of Desktop
Packages,
Eric,
your new test kernel works for... and screen-resizing works this time too.
To confirm, I am running the correct kernel build;
uname -a
Linux ubuntuvm1 4.15.0-53-generic #57+hf231164v20190620b11-Ubuntu SMP
Thu Jun 20 13:18:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bu
20190618 or
20190620. This installed Chromium 75.0.3770.80 or 75.0.3770.90 depending
on the date of the test.
In Ubuntu and Ubuntu Budgie the mouse pointer, when hovering over a
link, appears as an upward pointing black hand which is as expected.
But in Ubuntu MATE, Kubuntu, Lubuntu and Xubuntu the
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/b
Detailled instructions on how to use my ppa :
$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic
then reboot, and once login you can confirm if y
You can 'sudo snap connect chromium:mount-observe' for /etc/fstab.
/run/mount/utab is more complicated and you can read about it here:
https://forum.snapcraft.io/t/namespace-awareness-of-run-mount-utab-and-
libmount/5987
For the /run/udev/data accesses, can you paste the output of:
$ cat /run/ude
Removing packages from eoan:
libbonobo 2.32.1-3 in eoan
libbonobo2-0 2.32.1-3 in eoan amd64
libbonobo2-0 2.32.1-3 in eoan arm64
libbonobo2-0 2.32.1-3 in eoan armhf
libbonobo2-0 2.32.1-3 in eoan i386
libbonobo2-0
Removing packages from eoan:
libbonoboui 2.24.5-4 in eoan
libbonoboui2-0 2.24.5-4 in eoan amd64
libbonoboui2-0 2.24.5-4 in eoan arm64
libbonoboui2-0 2.24.5-4 in eoan armhf
libbonoboui2-0 2.24.5-4 in eoan i386
li
Removing packages from eoan:
gnome-vfs 1:2.24.4-6.1ubuntu2 in eoan
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan armhf
libgnomevfs2-
Removing packages from eoan:
orbit2 1:2.14.19-4 in eoan
liborbit-2-0 1:2.14.19-4 in eoan amd64
liborbit-2-0 1:2.14.19-4 in eoan arm64
liborbit-2-0 1:2.14.19-4 in eoan armhf
liborbit-2-0 1:2.14.19-4 in eoan i386
Removing packages from eoan:
libgnome 2.32.1-6 in eoan
libgnome-2-0 2.32.1-6 in eoan amd64
libgnome-2-0 2.32.1-6 in eoan arm64
libgnome-2-0 2.32.1-6 in eoan armhf
libgnome-2-0 2.32.1-6 in eoan i386
libgnome-2-0
Removing packages from eoan:
libgnome-keyring 3.12.0-1build1 in eoan
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan amd64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan arm64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan armhf
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: mutter (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
** Tags added: fixed-in-3.33.3 fixed-upstream
--
You received this bug notification because
Ok I managed to fix it
rm -rf ~/.config/chrome-remote-desktop/pulse*
Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
Ok I managed to fix it
rm -rf ~/.config/chrome-remote-desktop/pulse*
Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
Here is the last of the output after running the first test repo update
command in comment #73 on the Bug1832138VM.zip VM I built.
I'm guessing either there is an integrity issue upstream or more likely
there is a missing step so that a system that has been using the default
repo settings is super
** Description changed:
+ [Impact]
+
+ With most recent version of mutter installed.
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive)
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at t
After building and testing:
"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"
the above seems to do the trick ^ which will make the SRU easier (only one
commit).
I just don't know why the kernel git bisect testing found another commit, but
anyw
Here the journalctl info
I tested the Hotspot option with or without docking station.
Let me know if you need anything else
** Attachment added: "journal.zip"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+attachment/5271861/+files/journal.zip
--
You received th
Preliminary investigation: the code in chromium responsible for looking
up the theme color for the header bar is there:
https://cs.chromium.org/chromium/src/chrome/browser/ui/libgtkui/gtk_ui.cc?type=cs&l=864.
Outside of the snap confinement, the query for "#headerbar.header-
bar.titlebar" returns
I finally posted on the pulseaudio list and someone referred me to this
bug:
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640
I uninstalled timidity and that seems to have fixed the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which
cdebconf-terminal also build-depends on libvte-dev, this should be
resolved first before we do an Ubuntu-specific removal.
** Also affects: cdebconf-terminal (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, w
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832651
Title:
jackdbus fails to start: cannot allocate memory
Status in systemd:
Fix Released
Status
** Also affects: systemd (Ubuntu Eoan)
Importance: High
Status: Confirmed
** Also affects: jackd2 (Ubuntu Eoan)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
h
I already did that test ^ using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.
But based on last duflu update, I as I said I will now give a try again
Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.
--
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/1832138
Title:
Login scr
Public bug reported:
Some OEM store the commercial name of the product into the Family field
of the system information record of smbios.
Please add this fied to ubuntu-report.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-report 1.5.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-gener
This bug was fixed in the package gnome-settings-daemon -
3.32.1-1ubuntu2
---
gnome-settings-daemon (3.32.1-1ubuntu2) eoan; urgency=medium
* debian/patches/ubuntu_ibus_configs.patch:
- Always call add_ibus_sources_from_locale() during the first run
of g-s-d. This ensures t
Apologies for the delay, was busy with college work. I recall having
this bug on Ubuntu 16.04 and 17.04 too. I will have to install and see.
Also, this bug exists on Kubuntu (not surprising) Fedora, Manjaro (both
latest kernels and updates) . I tried digging up more info on hp-wmi
etc. but nothing
In the .H files of the libappindicator I have found 2 authors' e-mails:
Ted Gould and Cody Russell
. I have written email and received the
email-daemon answer that this e-mails are not valid. I see the problem
and want to know who can help me to find the decision.
Could you be so kind to direct m
For the record: Upstream bug is at
https://bugs.launchpad.net/hplip/+bug/1036236. But projects are linked.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1036236
Title:
hpcups and hpijs
Hello J T,
thanks for reporting that this is still a problem. I had originally filed this
report in 2012, but since it never moved forward I just resigned and kept using
the HPIJS driver, which produces much better (in terms of visually accurate)
output. However, Till Kamppeter says that Ubuntu
i only see chrome device as output device after manually running
pulseaudio -D and pulseaudio --check
** Attachment added: "Screenshot from 2019-06-20 12-58-29.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833534/+attachment/5271795/+files/Screenshot%20from%202019-06-20%2012-
Public bug reported:
in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.
I have excatly same problem on PC where configuration is completely
different than my lapt
** Attachment added: "after run pulseaudio -D and pulseaudio --check"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271788/+files/Screenshot%20from%202019-06-20%2012-58-29.png
--
You received this bug notification because you are a member of Desktop
Packages,
More info after i run pulseaudio --check i can see an output device but
its not my sound card, another screenshot attached
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1833527
Titl
** Attachment added: "Screenshot from 2019-06-20 12-46-32.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271783/+files/Screenshot%20from%202019-06-20%2012-46-32.png
--
You received this bug notification because you are a member of Desktop
Packages, which i
Public bug reported:
in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.
I have excatly same problem on PC where configuration is completely
different than my lapt
J T, you are posting your auto-generated bug data here but do not post a
comment telling what is exactly your observation.
Note that in HPLIP upstream HPIJS is still contained but not further
developed. We also do not explicitly support it any more in Ubuntu, we
encourage users to switch to hpcups
Hello gf.
I am not Rüdiger, the original submitter of this bug, but I am affected
by it. Since Rüdiger has not posted to this bug report in over 7 years,
I am posting to it to let you know that:
1) It *is* still a problem,
2) I *am* still interested in finding a solution to this bug,
and
3) I wou
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271759/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/103623
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271758/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271757/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271755/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271756/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Locale.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271750/+files/Locale.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/103623
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271754/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271752/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1036236
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271749/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271748/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271751/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1036236
apport information
** Attachment added: "PrintingPackages.txt"
https://bugs.launchpad.net/bugs/1036236/+attachment/5271753/+files/PrintingPackages.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.laun
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CupsErrorLog:
W [20/Jun/2019:09:16:39 +0100] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'serverLaser.hpijs-Gray..\' already exists
W [20/Jun/2019:09:16:39 +0100] CreateProfile failed:
org.fr
Workaround for mutter proposed here:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083
--
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/1832138
Title:
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083
--
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/1832138
Title:
Login sc
Please:
1. Wait till the problem happens again and let the system shut down.
2. Power up the system and then run:
journalctl -b-1 > prevboot.txt
3. Attach the file 'prevboot.txt' to this bug.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
S
This bug was fixed in the package glib2.0 - 2.60.4-1
---
glib2.0 (2.60.4-1) experimental; urgency=medium
* New upstream release (LP: #1832457)
+ Fixes to improved network status detection with NetworkManager (#1788)
+ Leak fixes to some `glib-genmarshal` generated code
+ Furt
Public bug reported:
the system shuts down automatically withouot any warnings. using sony
vaio laptop with only ubuntu installed on it.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.1
And the problem is indeed the kernel advertising
DRM_CAP_TIMESTAMP_MONOTONIC but instead of using CLOCK_MONOTONIC it is
really using CLOCK_REALTIME. This confirms kernel commit 37efe80ce85f is
the fix, but it may well have some prerequisite commits we haven't fully
worked out...
https://git.kernel
I am now able to reproduce and debug the problem. Indeed it is what I
said in comment #31.
The vmwgfx driver in this old kernel is telling lies. It says the next
screen refresh is in 49 years from now. It should be within 16.6
milliseconds.
** Summary changed:
- Login screen never appears on vm
Hi,
I use Linux from about 1996 and Windows from the very first version 2.x
Both OS have become more reliable and powerfull.
For Ubuntu the worst weaknesses are related to multimedia and conflicts
between devs : Graphics cards, sound issues and many other boring things
are really where Canonical
UPDATE: No, removing djvulibre-desktop solved the problem only for the
_multipage_ DjVu files, but not for the single-page ones. So, for a
single-page djvu files I still get the above-mentioned error message,
unless I manually add "image/vnd.djvu" to the end of MimeTypes in
/usr/lib/x86_64-linux-gn
** Description changed:
+ * Impact
+ Sometime multimedia keys stop working
+
+ * Test case
+ - start playing an audio file in VLC/totem/smplayer
+ - pause
+ - open a video in another player
+ - exit the other player
+ - try to resume the music play from the first one using the play key
+
+ -> i
Oops, typo in the previous comment: I wrote "evince filename,djvu" but
of course I meant "evince filename.djvu", i.e. with dot "." rather than
comma ",".
** Bug watch added: Debian Bug tracker #876710
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710
** Bug watch added: Red Hat Bugzilla
Oh sorry, I forgot to include the info you requested. I am using Ubuntu
Linux 18.04.2 and I don't use "nautilus". I always open djvu files using
the command "evince filename,djvu" from within terminal. Well, sometimes
I use "djview filename.djvu" (when I want to find out the resolution),
but normal
Also, here is some useful info for you:
$ apt list --installed | grep djvu
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
djvubind/bionic,bionic,now 1.2.1-5 all [installed]
djvulibre-bin/bionic,now 3.5.27.1-8 amd64 [installed,automatic]
djvulibre-desktop/bionic,b
1 - 100 of 112 matches
Mail list logo
