** Summary changed:
- Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor)
+ [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual
Monitor) since ~7th/8th May
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: regression-update
-
Per the upstream bug:
https://gitlab.gnome.org/GNOME/gnome-software/issues/642
The designation of apps in the Utilities folder is the job of gnome-
software:
https://gitlab.gnome.org/GNOME/gnome-software/blob/master/src/gs-
folders.c#L535
So we can remove the other tasks...
** Also affects
*** This bug is a duplicate of bug 1828613 ***
https://bugs.launchpad.net/bugs/1828613
Moved to bug 1828613
** This bug has been marked a duplicate of bug 1828613
See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [,
Realtek ALC889, Green Line Out, Rear] Playback problem
This sounds like bug 1821663. But because the fix for that bug is
specific to laptop/motherboard models, we should keep this bug separate.
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Summary changed:
- See - [Bug 1828569] [NEW] Popping sound when audio driver engaged - [,
Real
** Summary changed:
- [HP Notebook, Realtek ALC3227, Speaker, Internal] Playback problem.
+ [HP Notebook, Realtek ALC3227, Speaker, Internal] sound is very low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in U
User 'gdm' is normal and not a bug. That's the user which runs the login
screen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1828136
Title:
[Intel DH67CL, Realtek A
This bug is closed so if you have any ongoing problems then please open
a new bug by running:
ubuntu-bug bluez
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1788807
Title:
I put the attached file in if-pre-up.d/dummy-workaround
to make my system work reliably.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1828749
Title:
ifconfig dummy0 :
Here's the workaround.
** Attachment added: "workaround for ifconfig dummy0 bug"
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+attachment/5263317/+files/dummy-workaround
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
Desired behavior:
The ifconfig command should be able to deal with the
dummy device. This worked fine until recently.
Observed behavior:
:; ifconfig dummy0
dummy0: error fetching interface information: Device not found
This problem appeared when I upgraded to bion
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: icu (Ubuntu Disco)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: icu (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: icu (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: icu (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: icu (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.ne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: icu (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.n
A bit of a work around that worked for me is in the gdebi.desktop file
where it says "Terminal=false" change it to "Terminal=true" minus the
quotes of course. A "terminal window"(sort of) pops up behind the gdebi
window and allows you to install, reinstall ect. Don't know but it
installs packages f
** Changed in: alsa-plugins (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1817637
Title:
a52 DigitalAC-3Pulseaudio not wo
** Changed in: systemd
Status: New => Fix Released
--
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/1788048
Title:
systemd journald failed unmounting var
Status in s
By "we" do you mean official ubuntu-mate team ? In that case, contact me
on community.ubuntu.com.
Indicator-datetime requires lots of changes including the upcoming api
break from eds. Someone from community proposed to remove phone realted
code and go back to c. Not sure if it is still possible.
** Changed in: icu (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1827391
Title:
Japanese era Reiwa SRU
Status in icu packag
** No longer affects: evolution-data-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1828725
Title:
indicator-datetime does not have color squ
This bug reappears in 19.04 on ProBook 4520s.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1788807
Title:
Bluetooth device not detected after resume from suspend [Qualcomm
There are color squares in Ubuntu 12.04 LTS for both GTK2 and GTK3 versions of
`indicator-datetime`.
Squares are in place on 12.10, 13.04, 13.10.
There are no color squares in Ubuntu 14.04 LTS. So it first release
without them.
@Krusrshid, on Ubuntu MATE 19.10 we plan to use `indicator-datetime`
Why this is relevant in 19.10 ? Trusty already had eol.
Indicator-datetime was ported from C to C++ (r: 298) to work with
unity-8 and that feature gone missing with that. But there is no unity-8
anymore and the code doesn't work.
--
You received this bug notification because you are a member of
** Also affects: evolution-data-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1828725
Title:
ind
** Also affects: apport (Linux From Scratch)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/538097
Title:
+storeblob fails with
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1828725
Title:
indicator-datetime does not have color squares for different calendars
and
On my ubuntu 18.04 system I only have
/usr/bin/pulseaudio --start --log-target=syslog
owned by me. On my 19.04 system
/usr/bin/pulseaudio --daemonize=no
also owned by me. Note gdm is not running. I assume lightdm, which is
running, is the alternative.
--
You received this bug notification
my system is ubuntu 18.04. And from log ps:
The user of "/usr/bin/pulseaudio --daemonize=no" is gdm
The user of "/usr/bin/pulseaudio --start --log-target=syslog" is my
account.
If the user is differnt, I have no idea, maybe we should report the problem to
pulseaudio-disc...@lists.freedesktop.o
Seems to be regression.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1828725
Title:
indicator-datetime does not have color squares for different calendars
a
>From ps I see that "/usr/bin/pulseaudio --daemonize=no" is running with
user "adrian" and also my home directory is owned by "adrian".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launch
** Changed in: indicator-datetime (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: indicator-datetime (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Launchpad has imported 18 comments from the remote bug at
https://bugs.webkit.org/show_bug.cgi?id=143491.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.la
>From a security PoV this is basic security by obscurity and effectively
pointless - they are simply XORing each byte with a fixed value and then
base64 encoding it - since the source code is public anyone can easily
find this out and hence easily decode it - the only way to do this
securely would
** Attachment added: "indicator-datetime from Ubuntu 19.10 without coloured
squares"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1828725/+attachment/5263242/+files/ubuntu-19-10.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Public bug reported:
Steps to reproduce:
1. Install Ubuntu with `indicator-datetime` and `evolution`
2. Add event to *Personal* calendar (default color)
3. Add new calendar and name it for example *Work* (red color)
4. Create contact with two dates - birthday and anniversary (it is pink color)
Ex
A similar bug happened here on 2 different Ubuntu installs once they
upgraded to Ubuntu 18.10.
Another symptom of the bug was periodic addition of IPv6 addresses to
the `ip addr` listing. If you wait a while, the list had thousands of
IPv6 entries in it!
Apparently every time it decided to fetch
Could you also use the command
$ apport-collect -p alsa-base 1828569
To add the details of you soundcard/driver to the report?
--
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/bu
Thank you for your bug report, could you try if adding that option to the
kernel boot line helps?
snd_hda_intel.power_save=0
(https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter/19487
has tip on how to do that if you need directions)
** Changed in: pulseaudio (Ubuntu)
Thank you for your bug report. Could you add your journalctl log from a
boot that got the issue?
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
**
** Changed in: evolution-data-server (Ubuntu)
Importance: Undecided => High
** Changed in: evolution-data-server (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-
It would be good to have design input on that, I'm not convinced that
things like the system monitor, language-selector or usb creater should
be moved outside the main list. That folder split seems a bit random,
maybe it should be removed?
--
You received this bug notification because you are a m
GNOME upstream pointed out webkitgtk as the place where the works needs
to happen and to https://bugs.webkit.org/show_bug.cgi?id=143491 and a
fix was recently commited, hopefully it means it's going to be resolved
next cycle
** Bug watch added: bugs.webkit.org/ #143491
https://bugs.webkit.org/s
** Changed in: libva (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1813131
Title:
i965_drv_video.so doesn't load any more
Public bug reported:
sound is very low for videos both hevc and h264 . even with
amplification. and fine in youtube. overall sound is very much less
than when i was in windows 10
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0
Public bug reported:
This is an ubuntu 19.04 fresh [re]install
Previous installation was an upgrade 18.04 LTS (at least) -> 18.10 -> 19.04 and
the sound worked
Sound is expected on HDMI screen Dell S2415H
Sound level on screen is set to max
In system settings>sound , every sound entry is set to
In system settings>sound , every sound entry is set to mute (speaker slashed)
... and this can't be changed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1828713
Title:
48 matches
Mail list logo
