[Bug 1875114] Re: freeipa-server package missing on Ubuntu 20.04

2022-03-13 Thread Nils K
Since december last year the freeipa-server package is in the debian
experimental distribution
(https://packages.debian.org/experimental/freeipa-server). Sadly it
seems like it will not be included in 22.04 LTS - maybe as a backport if
one might hope once it lands in debian.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875114

Title:
  freeipa-server package missing on Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1875114/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] UdevDb.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1853273/+attachment/5306917/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] ProcCpuinfo.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306906/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Re: --force-dark-mode flag in init file does not get recognized

2019-11-21 Thread Nils K
Just to clarify, the --force-dark-mode flag works different from the
#enable-force-dark flag.

--force-dark-mode should instruct the browser to use a dark UI layout,
i.e. menus, omnibar etc.

#enable-force-dark instructs chrome to force a dark mode for websites
using different color inversion algorithms etc.

And --enable-features=WebUIDarkMode should instruct chrome to use a dark
mode on internal pages like chrome://settings and chrome://extensions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Snap.Info.core.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Snap.Info.core.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306914/+files/Snap.Info.core.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Snap.Connections.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Snap.Connections.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306912/+files/Snap.Connections.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Snap.Info.core18.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Snap.Info.core18.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306915/+files/Snap.Info.core18.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] ProcCpuinfoMinimal.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306907/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Snap.Info.chromium.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Snap.Info.chromium.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306913/+files/Snap.Info.chromium.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Lspci.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1853273/+attachment/5306905/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] ProcModules.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306910/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Snap.Info.gtk-common-themes.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Snap.Info.gtk-common-themes.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306916/+files/Snap.Info.gtk-common-themes.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Re: --force-dark-mode flag in init file does not get recognized

2019-11-21 Thread Nils K
apport information

** Tags added: apport-collected eoan snap wayland-session

** Description changed:

  When creating a init file at ~/.chromium-browser.init chromium is
  supposed to read flags from there. However these do not work correctly.
  
  
  What I expected to happen:
  Starting chromium with the --force-dark-mode flag in the init file should 
make it use a dark UI (as long as the GTK theme option in the settings is not 
used)
  
  What happened instead:
  Starting chromium with above configuration correctly echoes 
CHROMIUM_FLAGS="--force-dark-mode" to the terminal and it also appears under 
chrome://version but a normal non-dark UI is used.
  
  
  What does work:
  Starting chromium with the above flag as an argument from the terminal makes 
it use a dark UI (apparently not for everyone 
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/comments/5)
  
  What also does not work:
  This may affect all flags - so far I have tested the above and 
"--enable-features=WebUIDarkMode"
  
  
  Version:
  chromium version: 78.0.3904.97 rev: 937 tracking: stable
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DRM.card0-DP-1:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64: 
+  modes:
+ DRM.card0-DP-2:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64: 
+  modes:
+ DRM.card0-HDMI-A-1:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64: 
+  modes:
+ DRM.card0-HDMI-A-2:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64: 
+  modes:
+ DRM.card0-eDP-1:
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wAw5DgFAAAaAQSVIhN46qHFlFlXjycgUFQBAQEBAQEBAQEBAQEBAQEBLjaAoHA4H0AwIDUAWMIQAAAatiyA9HA4FkAwIDUAWMIQAAAa/gBMRyBEaXNwbGF5CiAg/gBMUDE1NldGNi1TUEs0AJw=
+  modes: 1920x1080 1920x1080
+ DiskUsage:
+  Filesystem  Type   Size  Used Avail Use% Mounted on
+  /dev/mapper/ubuntu--vg-root ext4   233G  188G   34G  85% /
+  tmpfs   tmpfs  3,9G   99M  3,8G   3% /dev/shm
+  /dev/mapper/ubuntu--vg-root ext4   233G  188G   34G  85% /
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-04-30 (204 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
+  Bus 001 Device 003: ID 04f2:b5c0 Chicony Electronics Co., Ltd Integrated 
Camera
+  Bus 001 Device 002: ID 0cf3:e500 Qualcomm Atheros Communications 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 20H5006VGE
+ Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 [modified: 
usr/share/applications/chromium-browser.desktop]
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
+ Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.97 
(021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859})
+ Snap.ChromiumVersion:
+  CHROMIUM_FLAGS="--force-dark-mode --enable-features=WebUIDarkMode"
+  Chromium 78.0.3904.97 snap
+ Tags:  wayland-session eoan snap
+ Uname: Linux 5.3.0-23-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare 
sudo wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 10/30/2017
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: R0DET88W (1.88 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20H5006VGE
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrR0DET88W(1.88):bd10/30/2017:svnLENOVO:pn20H5006VGE:pvrThinkPadE570:rvnLENOVO:rn20H5006VGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad E570
+ dmi.product.name: 20H5006VGE
+ dmi.product.sku: LENOVO_MT_20H5_BU_Think_FM_ThinkPad E570
+ dmi.product.version: ThinkPad E570
+ dmi.sys.vendor: LENOVO

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306903/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Snap.ChromiumPrefs.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Snap.ChromiumPrefs.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306911/+files/Snap.ChromiumPrefs.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] Dependencies.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306904/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] ProcInterrupts.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306909/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] ProcEnviron.txt

2019-11-21 Thread Nils K
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1853273/+attachment/5306908/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851896] Re: [snap] Changes in desktop file get overwritten

2019-11-20 Thread Nils K
Okay, I just did, you can find it under
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851896

Title:
  [snap] Changes in desktop file get overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1853273] [NEW] --force-dark-mode flag in init file does not get recognized

2019-11-20 Thread Nils K
Public bug reported:

When creating a init file at ~/.chromium-browser.init chromium is
supposed to read flags from there. However these do not work correctly.


What I expected to happen:
Starting chromium with the --force-dark-mode flag in the init file should make 
it use a dark UI (as long as the GTK theme option in the settings is not used)

What happened instead:
Starting chromium with above configuration correctly echoes 
CHROMIUM_FLAGS="--force-dark-mode" to the terminal and it also appears under 
chrome://version but a normal non-dark UI is used.


What does work:
Starting chromium with the above flag as an argument from the terminal makes it 
use a dark UI (apparently not for everyone 
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/comments/5)

What also does not work:
This may affect all flags - so far I have tested the above and 
"--enable-features=WebUIDarkMode"


Version:
chromium version: 78.0.3904.97 rev: 937 tracking: stable

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853273

Title:
  --force-dark-mode flag in init file does not get recognized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853273/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851896] Re: [snap] Changes in desktop file get overwritten

2019-11-19 Thread Nils K
When I however add in the init file it gets sourced and shows up in
chrome://version but does not work as prefers-color-scheme is still
light. If I supply it at the command line it correctly works but shows
up twice on chrome://version. Should I report this in a seperate bug or
in the chromium bug tracker?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851896

Title:
  [snap] Changes in desktop file get overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851895] Re: [snap] No access to HTML documentation in /usr/share/doc

2019-11-19 Thread Nils K
Okay and theoretically I should be able to remount the /usr/share folder
as a loopback in media, right? But that would be a needlessly
complicated solution. Would reinstalling the snap in classic mode fix
the problem?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851895

Title:
  [snap] No access to HTML documentation in /usr/share/doc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851895/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851896] Re: [snap] Changes in desktop file get overwritten

2019-11-19 Thread Nils K
Yes it probably was. I did not thought about snap overwriting that file.
Thanks for the tip, I will do so.

I am curious though - is the init file generally looked for by the
default chromium build or the snap?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851896

Title:
  [snap] Changes in desktop file get overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851895] Re: No access to local files outside /home

2019-11-14 Thread Nils K
This also (kinda obvious, but did not thought about it first) affects
saving files outside of ones home folder.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851895

Title:
  No access to local files outside /home

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851895/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851896] [NEW] Changes in desktop file get overwritten

2019-11-08 Thread Nils K
Public bug reported:

Changes in the chromium_chromium.desktop file get overwritten.
This includes flags like --force-dark-mode etc.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851896

Title:
  Changes in desktop file get overwritten

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851895] [NEW] No access to local files outside /home

2019-11-08 Thread Nils K
Public bug reported:

Due to the fact that snaps are very restricted one is unable to open local 
files outside of ones own home directory.
An example where such an access is common are files from *-doc packages like 
`/usr/share/doc/python3-doc/html/index.html`.
I don't know if this is fixable with the current interfaces or if this requires 
a classic confinement mode but I miss this feature as sometimes running a 
webserver is not an option...

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851895

Title:
  No access to local files outside /home

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851895/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816210] [NEW] Failed at stage "init" beccause it could not parse "ip addr show"

2019-02-15 Thread Nils K
Public bug reported:

Environment: Virtuozzo
Cloud provider: Strato AG Germany

Cloud-init was manually installed after first boot to simplify server
setup.


Minimal cloud-init configuration which leads to failure:

  #cloud-config
  cloud_init_modules:
- users-groups

  users:
- name: username


Output of "ip addr show":

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: venet0:  mtu 1500 qdisc noqueue 
state UNKNOWN group default 
link/void 
inet 127.0.0.1/32 scope host venet0
   valid_lft forever preferred_lft forever
inet 85.214.226.67/32 brd 85.214.226.67 scope global venet0:0
   valid_lft forever preferred_lft forever
inet6 2a01:238:427f:2300:c8a3:3e40:399f:3ddd/128 scope global 
   valid_lft forever preferred_lft forever
inet6 ::2/128 scope global 
   valid_lft forever preferred_lft forever

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cloud-init 18.4-0ubuntu1~18.04.1
Uname: Linux 4.15.0 x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CloudName: Other
Date: Sat Feb 16 02:34:53 2019
PackageArchitecture: all
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
logs.tgz: Error: [Errno 2] No such file or directory: '/tmp/cloud-init-logs.tgz'
modified.conffile..etc.cloud.cloud.cfg: [deleted]
modified.conffile..etc.cloud.cloud.cfg.d.05_logging.cfg: [deleted]
modified.conffile..etc.cloud.cloud.cfg.d.README: [deleted]
user_data.txt: Error: [Errno 2] No such file or directory: 
'/var/lib/cloud/instance/user-data.txt'

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816210

Title:
  Failed at stage "init" beccause it could not parse "ip addr show"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1816210/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs