Seems this lines of code are responsible:
src/dns/nm-dns-systemd-resolved.c:
static void
add_domain (GVariantBuilder *domains,
const char *domain,
gboolean never_default)
{
/* If this link is never the default (e.g. only used for resources on
this
*
nope, won't happen, and 12.04 is EOL soon anyway, if not already
** Changed in: mesa-lts-xenial (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa-lts-xenial in Ubuntu.
It appears the startpage in recent versions of chromium is hardcoded to a
custom view that displays most visited pages as well as a google search box if
google is the current search engine.
I couldn't find any preference for users to set a custom start page.
** Changed in: chromium-browser
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1514484
Title:
Chromium start-up script doesn't
Closing now, as this was affecting an old version of chromium-browser.
Please file a new bug if you're still having memory issues with
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member
Public bug reported:
banshee crashes while importing music to the library
lsb_release -rd
Description:Ubuntu 17.04
Release:17.04
apt-cache policy banshee
banshee:
Installiert: 2.9.0+really2.6.2-7ubuntu2
Installationskandidat: 2.9.0+really2.6.2-7ubuntu2
** Attachment added: "Output of xrandr with monitors connected to DP of the
dock and to HDMI connector of the laptop"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1686333/+attachment/4868158/+files/xrandr.out
--
You received this bug notification because you are a
Public bug reported:
e7440 Latitude / Dell Dock
Description:Ubuntu 16.04.2 LTS
Release:16.04
xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
The docking station maps DP1 port of the laptop to two outputs at the
back panel mirroring the picture.
Earlier (in 14.04) it
** Branch linked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1664007
Title:
package gnome-keyring 3.20.0-2ubuntu4 failed to
I have the same problem on 16.04.2 Xenial since upgrading the Kernel to
4.4.0-75 yesterday.
Booting the the older kernel version 4.4.0-72-generic seems to be a workaround.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
*** This bug is a duplicate of bug 1679903 ***
https://bugs.launchpad.net/bugs/1679903
** Branch linked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
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/1686189
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => ali salama (alisalama)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1667113
Title:
System users appears in
Public bug reported:
[Impact]
Mesa stable release for zesty & backport to xenial.
[Test case]
Install, run desktop session, test xonotic.
the important hw drivers to test:
- i965 (Intel)
- radeonsi (AMD)
[Regression potential]
Spec compliance test suites are already run by Intel and others,
Public bug reported:
Ubuntu Gnome 17.04, apt update-ed
When installing inkscape with apt install inkscape, the installation
fails complaining on missing depends:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
Yes, what Amr said...
$ dpkg -s light-themes | grep Source
Source: ubuntu-themes
** Changed in: light-themes (Ubuntu Artful)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to light-themes in Ubuntu.
The default location provider in chromium-browser is network-based, it
doesn’t look like it knows how to talk to GPS hardware.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This isssue is not relevant to VPN connections only but also for normal
workin local network. systemd-resolve and systemd-resolved stub listener
are behaving differently - the stub does not accept the domain/search
domains sent by DHCP. THis is really weird. Isn't the issue in
domain/search
Public bug reported:
I don't speak english, i speak french.
Sorry, thank you.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
.tmp.unity_support_test.0:
ApportVersion:
Public bug reported:
XX
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgstreamer0.10-0 0.10.36-1.5
ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21
Uname: Linux 4.4.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Wed Apr 26 10:49:08 2017
sir, where is the location for dkms build log ?
2017-04-21 8:42 GMT+07:00 Daniel van Vugt
:
> Thanks for your bug report but we need the DKMS build log for the nvidia
> module to see what failed.
>
> Sorry I can't recall where that is right now.
>
> ** Changed in:
** Branch linked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1174162
Title:
chrome-browser makes gnome-keyring-daemon use
Precise is not supported any longer.
The version in trusty currently is 53.0.2785.143 and it should shortly be
updated to 58.0.3029.81.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Thank you. I've been testing the ppa version, and it works fine. The two
noticeable issues are that chromecast doesn't work anymore (known
upstream issue I guess), and flash's behaviour isn't the same as chrome.
--
You received this bug notification because you are a member of Desktop
Packages,
** Changed in: network-manager-applet (Ubuntu)
Assignee: (unassigned) => Rohan (rohanmiskin)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1684967
Title:
[17.04
I’ve packaged chromium-browser 58.0.3029.81 for trusty, it is being
validated by the security team and will hopefully hit -updates soon.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Status:
Hi Ali,
as I outlined before the fix likely has to take place in accountsservice not in
libvirt.
You assigned yourself, so I wanted to ask what you have in mind to do?
In case this was an accident you might want to unassign yourself, but
"subscribe" [1] you to the bug to stay up to date on this
Those workarounds will affect scrollbars for everything.
Chris, any chance you could take a look and/or forward the bug please?
It seems 52 is using more of the GTK theming but still not enough - now
the hovering bits aren't working properly with our theme.
There might be a way to target a
** Branch unlinked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1664007
Title:
package gnome-keyring 3.20.0-2ubuntu4 failed
*** This bug is a duplicate of bug 1679903 ***
https://bugs.launchpad.net/bugs/1679903
** Branch unlinked: lp:~cjwatson/launchpad/snap-find-by-url-prefixes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
AFAICT everything requested by the OP is implemented in recent versions
of chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit in Ubuntu.
accepted -0ubuntu0.16.04.2 to -proposed
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
Hi.
Thanks for quick response.
You're mentioning that I need to use prime-select.
Do you have a link on how I should proceed with on terminal or in a
different fashion.
My concern is that I have a built machine and really want to use
Ubuntu/Linux distro. Nvidia drivers is for my need to do
This bug was fixed in the package chromium-browser -
58.0.3029.81-0ubuntu0.14.04.1172
---
chromium-browser (58.0.3029.81-0ubuntu0.14.04.1172) trusty; urgency=medium
* Upstream release: 58.0.3029.81
- CVE-2017-5057: Type confusion in PDFium.
- CVE-2017-5058: Heap use after
I don't have any way of verifying this since I don't use chromium anymore,
sorry.
On Wed, Apr 26, 2017 at 1:10 AM Olivier Tilloy
wrote:
> @James: are you still seeing this issue with recent releases of
> chromium?
>
> --
> You received this bug notification because
The upstream bug was closed due to lack of interest/inactivity.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This bug was fixed in the package chromium-browser -
58.0.3029.81-0ubuntu0.14.04.1172
---
chromium-browser (58.0.3029.81-0ubuntu0.14.04.1172) trusty; urgency=medium
* Upstream release: 58.0.3029.81
- CVE-2017-5057: Type confusion in PDFium.
- CVE-2017-5058: Heap use after
** Changed in: gnome-settings-daemon (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1686077
Title:
Own
Closed down Pidgin. Waited a few seconds for all the defunct processes
to go away. Restarted Pidgin. Probably only a minute later before the
first defunct process has arrived.
I am signed into 4 IRC channels automatically on startup. I have tried
to send my identify command to the NickServ
It has been noted on the developer site for Pidgin that 1 defunct is
normal for DNS lookups.
https://developer.pidgin.im/ticket/15617#comment:11
The rest I have seen might come from failed attempts to connect to chat
services. https://developer.pidgin.im/ticket/15617#comment:13 mentions
you get
Well I am seeing something odd in Pidgin.
$ ps -elf | grep defunct | wc -l
121
$ ps -elf | grep defunct | grep pidgin | wc -l
120
(One of the 'defunct' hits is the grep)
$ pidgin --version
Pidgin 2.10.12 (libpurple 2.10.12)
I have IRC, and XMPP to GoogleMail (Hangouts / Talk) configured and
@Chris: I'm not 100% sure, for my home machine it was either a Radeon HD
4850 or a Radeon R7 200 series.
I think this bug was "fixed" on both machines once I upgraded to Ubuntu
15.10. (Although on my work machine 15.10 caused a different system
freeze bug starting with that release that didn't
** Description changed:
[Impact]
Mesa stable release for zesty & backport to xenial.
[Test case]
Install, run desktop session, test xonotic.
the important hw drivers to test:
- i965 (Intel)
- radeonsi (AMD)
[Regression potential]
Spec compliance test suites are
** Changed in: evince
Status: Unknown => Confirmed
** Changed in: evince
Importance: Unknown => Medium
--
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/1660353
Title:
chromium-browser still depends on libgconf-2-4. I think you should drop
the Build-Depends: libgconf2-dev and set use_gconf=false in
debian/rules. Also, the apport script shouldn't try to use gconf either.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Released => Confirmed
**
Not sure what causes the problem or how to fix it manually but a reboot
cleared it up for me (same exact error message from terminal as original
reporter). So after reboot it is working fine again. This is Ubuntu
16.04, btw.
--
You received this bug notification because you are a member of
Running
# apt-get upgrade
has given me the following errors for one month now:
cups : Depends: cups-daemon (>= 2.1.3-4ubuntu0.2)
cups-core-drivers : Depends: cups-daemon (>= 2.1.3-4ubuntu0.2)
cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is installed
As a result I have not
I can reproduce the black screen thing with Faerie on radeon hw, but
installing libgles1-mesa doesn't help. So it's just a bug in the radeon
DRI driver.
** Changed in: mesa (Ubuntu)
Status: Won't Fix => Triaged
** Summary changed:
- Missing libgles1 in Ubuntu 17.04 repos triggers issues
Clémence have you tried Ed's solution
(https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/comments/14)
? It worked for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1676621
*** This bug is a duplicate of bug 1451728 ***
https://bugs.launchpad.net/bugs/1451728
if you need a quick fix solution to this here it is:
```
$ sudo dpkg --remove kaccounts-providers
```
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Sorry for spamming everyone, as this started happening after a kernel
upgrade is it a Kernel bug?
--
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/1686189
Title:
External monitor
Hi,
I have been testing again the chromecast with last upload, and it is
still the same thing.
chromecast is not seen in chromium (it is seen with a chrome) and avahi
still see the chromecast.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Released => Confirmed
--
You received
Upstream bug marked wontfix.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/535235
Title:
** Summary changed:
- corrupt gfx with Faeria/Payday 2 on Radeon
+ [radeon] corrupt gfx with Faeria/Payday 2
--
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/1682913
Title:
[radeon]
Closing due to the last update to this bug being 6 years old. Please
file a new bug if this still applies to recent releases of chromium-
browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of
Closing due to the last update to this bug being 6 years old. Please
file a new bug if this still applies to recent releases of chromium-
browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/590572
Title:
Chromium ignores cookie exceptions
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Closing due to the last update to this bug being 6 years old. Please
file a new bug if this still applies to recent releases of chromium-
browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
** Tags removed: lucid raring saucy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/882942
Title:
NaCL is missing
Status in chromium-browser package in Ubuntu:
Triaged
I confirm that the bug is still there...
--
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/1639203
Title:
mouse cursor flashing on laptop screen after adding second monitor
through usb
Closing due to the last update to this bug being almost 6 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Closing due to the last update to this bug being 6 years old. Please
file a new bug if this still applies to recent releases of chromium-
browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
This appears to be fixed in recent releases of chromium.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
By definition the custom title bar is custom. That said, middle click on
the custom title bar seems to minimize the window by default.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages,
** Tags removed: lucid maverick natty oneiric
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Sounds like a bug in compiz, not in the browsers.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
** Changed in: firefox (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Closing due to the last update to this bug being almost 6 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
Sounds like a corrupted profile.
Anyway, closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/663346
Title:
Chromium widget unusable in 10.10
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Not sure what QRT is/was, but given the age of that bug, it should be
safe to close.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 675457 ***
https://bugs.launchpad.net/bugs/675457
** This bug has been marked a duplicate of bug 675457
Chromium browser does not change spell checking language
--
You received this bug notification because you are a member of Desktop
Packages, which is
Closing due to the last update to this bug being 6 years old. Please
file a new bug if this still applies to recent releases of chromium-
browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of
Still valid. The packages are built with enable_nacl=false.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/882942
Title:
NaCL is missing
Status in chromium-browser package
Alright, that seems fair. I'd guess much like you guessed that the rest
came from failed connection attempts during that period where the network
was unavailable. Yes, Pidgin having one defunct process for DNS lookups is
totally normal (and honestly something we all wish they'd put in the damn
chromium-browser-l10n is now a recommends of chromium-browser, so "apt
install" and GUI frontends will all install it by default.
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 586318 ***
https://bugs.launchpad.net/bugs/586318
** This bug has been marked a duplicate of bug 586318
Cannot quit Chromium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Closing due to the last update to this bug being almost 7 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete =>
** Changed in: chromium-browser (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/631153
Title:
package chromium-browser-l10n (not
Closing per comment #3, and because this appears to be fixed. On my
machine where chromium is my preferred browser, the default alternative
remains firefox:
$ LANG=C sudo update-alternatives --config gnome-www-browser
There are 2 choices for the alternative gnome-www-browser (providing
Hi, thanks for your answer.
I had indeed tried it and it fails, unfortunately, with the following messages:
cups-daemon is already the newest version (2.1.3-4).
printer-driver-gutenprint is already the newest version (5.2.11-1).
printer-driver-gutenprint set to manually installed.
cups-filters is
Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Closing due to the last update to this bug being almost 6 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member
@Reuben: is this still a problem with recent releases of chromium-
browser?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/708311
Title:
Manually added startup application
Closing due to the last update to this bug being almost 6 years old.
Please file a new bug if this still applies to recent releases of
chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member
This appears to work in recent releases of chromium-browser.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Thanks for the feedback Reuben. Closing now.
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/708311
Probably. However I just tested on unity7 and no notification shows up.
This seems to work only in gnome-shell. So not something that can be
enabled by default for now.
** Changed in: chromium-browser (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug
Public bug reported:
After a fresh install of Rhythmbox, trying to run from the app launcher
in GNOME desktop results in the attempted-opening-rhythmbox instance
unresponsive. After ten or fifteen seconds, it says this program has
failed to respond, and asks me to Wait or Force Quit the program.
No. I can confirm.
SFTP (basically SSH) mounts from nautilus can be opened from vlc, but
not FTP and possibly SMB as well.
With FTP mount the symptoms are exactly as
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/211632/comments/9
--
You received this bug notification because you are a
1 - 100 of 200 matches
Mail list logo