It seems on upgrades/downgrades (by apt install) auto state of a package
is kept even without --mark-auto, if there is a reverse dependency of
the package installed. But with same command, if the version happens to
be the same in the repository, the package is marked as manually
installed. So if I
And the with the same option (without --mark-auto) it would not change
any package marked as manual to auto.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100937
Title:
apt install --mark-auto does
Public bug reported:
e.g.
1) sudo apt install ppa-purge
2) sudo apt-mark auto ppa-purge
3) sudo apt install --mark-auto ppa-purge
Expected result:
ppa-purge is marked as auto
What happend:
ppa-purge is marked as manual
If line (2) is omitted, I think the result should be manual, even if it
is u
Public bug reported:
The syntax of "apt-mark minimize-manual" command is not shown in the
synopsis. Could you give it a meta-package argument to mark dependencies
of it as auto or something like that?
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apt 2.7.14build2
ProcVersionSignature: Ubu
The fix was never released in ppa-purge package of Universe repository
of Ubuntu, so I guess it isn't needed anymore. I don't have any test
repository, either so I guess I remove my soname bump code in my fork.
https://askubuntu.com/questions/1457705/are-there-ppas-with-soname-bumps
--
You recei
** No longer affects: xinput-calibrator
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2094896
Title:
xinput can not enable pointer device by name
To manage notifications about this bug go to:
https
So it tells it is fixed in xinput-calibrator, but it is closed, not
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2094896
Title:
xinput can not enable pointer device by name
To manage notifi
** Bug watch added: gitlab.freedesktop.org/xorg/app/xinput/-/issues #16
https://gitlab.freedesktop.org/xorg/app/xinput/-/issues/16
** Also affects: xinput-calibrator via
https://gitlab.freedesktop.org/xorg/app/xinput/-/issues/16
Importance: Unknown
Status: Unknown
--
You received
Bonus issue: If I disable 'pointer:Logitech K400' or 'pointer:bcm5974'
(which is the integrated touchpad or the notebook) in Xubuntu 20.04, the
latter stops working and I can not make it work by xinput commands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
IIRC the feature worked by Xubuntu 20.04 before, but now it does not
even there: xinput version 1.6.3, XI version on server: 2.3. In Xubuntu
24.04 xinput version is 1.6.4 and XI version on server is 2.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
As you can see in the in the terminal output, disabling the device
worked without error by the same name so I think enabling should work,
too.
I think it is inappropriate to advertise your tool here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
Here is some terminal output:
$ xinput list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ Logitech USB-PS/2 Optical Mouse id=10 [slave pointer (2)
Still occurs with linux 6.8.0-51-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855678
Title:
Will not suspend, if I have Native Instruments Audio Kontrol 1
connected
To manage notificati
Well, -t doesn't work, if I want to downgrade packages after disabling a
PPA repository. I have to add for each argument
separately. I think the system should support easy downgrade when some
PPAs are removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
Suppose package x has greater version than the latest one in
repositories.
sudo apt-get install -t=$(lsb_release -cs) x
does not downgrade the package, but
sudo apt-get install x/$(lsb_release -cs)
does.
I don't see why it shouldn't downgrade by the first command, too.
B
6.5.0-44-generic seems to work fine with the new cable, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009672
Title:
Regression: Unable to show the native 1920x1080 mode in
HDMI/DisplayPort o
Using another HDMI cable fixed this with 5.15 kernel. 6.8.0-40-generic
freezes on boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009672
Title:
Regression: Unable to show the native 1920x1080 m
Occurs with 5.15.0-115-generic, too. That is the current default kernel
of Xubuntu 22.04.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009672
Title:
Regression: Unable to sh
*** This bug is a duplicate of bug 2009672 ***
https://bugs.launchpad.net/bugs/2009672
I reported this bug against xorg. I wonder why it is set to
xfce4-settings package? The issue is also when I use xrandr to change
modes. How could it be desktop environment specific? Well, maybe it does
not
Public bug reported:
I noticed this issue after upgrade from 20.04 to 22.04 (Xubuntu). HDMI-1
(which is DP-1 with an adapter) can not show rates better than 30Hz in
1920x1080 resolution. Another monitor is in DP-2 and can function at
2560x1440 74.97Hz, but the issue with HDMI-1 is also in single m
Public bug reported:
Some Super + key keyboard shortcuts are set to launch some Xubuntu
applications by default. They are hard to remember, and the shortcuts
may be pressed accidentally, so IMO it is better to not set these
shortcuts by default. Especially Super + digit shortcuts are
unintuitive.
So there is neither /etc/apt/apt.conf.d/01autoremove-kernels nor
/etc/kernel/postinst.d/apt-auto-removal anymore. Anyway I could not make
'apt autoremove' try to remove current kernel anymore. Tested by apt
2.0.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Test passed for apt 2.0.8
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968154
Title:
Only keep 2 kernels
To mana
** Description changed:
$ lsusb
..
Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1
..
If I have the device connected when I choose suspend to RAM then display
blanks, suspend fails and system does not respond to any user input
except power button.
Workarou
** Description changed:
$ lsusb
..
Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1
..
If I have the device connected when I choose suspend to RAM then display
blanks, suspend fails and system does not respond to any user input
except power button.
+ Workarou
Still present in 5.13.0-27-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855678
Title:
Will not suspend, if I have Native Instruments Audio Kontrol 1
connected
To manage notifications a
** Also affects: lightdm
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/1946987
Title:
Regression: Nvidia 340 Xorg driver is installed but not loaded after
** Summary changed:
- Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
+ Regression: Nvidia 340 Xorg driver is installed but not loaded after OS
upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Description changed:
I tried both nouveau and nvidia-340 drivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, cur
Please ask in askubuntu.com.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875025
Title:
Cannot enter password to unlock session
To manage notifications about this bug go to:
https://bugs.launchpa
Related question: https://askubuntu.com/q/1370465/21005
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946987
Title:
Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
To manage no
Maybe lightdm could do something differently? What causes HDMI to appear
when I log out of session?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946987
Title:
Nvidia 340 Xorg driver is installed b
** Description changed:
I tried both nouveau and nvidia-340 drivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, cur
What does the "Report problem..." button in the dialog do, then if I
have to use command line to report the crash files?
I see "sudo nvidia-xconfig" generates some basic /etc/X11/xorg.conf
file.
Regardless, I noted the following:
If I log out from the Xfce session back to the LightDM greeter the
BTW after every boot I see "System program problem detected?" dialog and
every time I choose "Report problem...". I booted today, too.
$ LC_ALL=C ls -l /var/crash/
total 4624
-rw-r- 1 jarnos whoopsie 1416740 Oct 14 11:05
_usr_bin_xfce4-power-manager.1000.crash
-rw-r- 1 root whoopsie 331
Where can those differences be? I could compare to another machine with
the same driver. The graphics card is different, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946987
Title:
Nvidia 3
Could there be something in upgrading process that caused this that
clean install wouldn't have done? Could the relevant parts be clean
installed now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946
One more thing. I get an error dialog after startup in the desktop. It
does not tell what went wrong, but it has an option to report to
developers and so I did.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Hmm. I have another computer that is more successful with nvidia-340 in
Xubuntu 20.04. When I compare to Xorg.0.log files, I see differences
after line
"(II) systemd-logind: logind integration requires -keeptty and -keeptty
was not provided, disabling logind integration". The successful one has
"
I searched for all .conf files in the device for "fbdev" (case
insensitive) and found these:
/usr/src/linux-headers-5.4.0-84-generic/include/config/auto.conf
CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_DRM_FBDEV_EMULATION=y
CONFIG_DRM_FBDEV_OVERALLOC=100
/usr/src/linux-headers-5.4.0-84-generic/include/con
There is no string "Default Screen Section" in
/usr/share/X11/xorg.conf.d directory.
The directory contains files: 10-amdgpu.conf
10-quirks.conf
10-radeon.conf
40-libinput.conf
51-synaptics-quirks.conf
70-synaptics.conf
70-wacom.conf
nvidia-drm-outputclass-ubuntu.conf
The last one is attached.
*
I don't know if it is relevant, but even with Xubuntu 18.04 I had to
force pulseaudio sample rate to 44100 to be able to successfully play
sound via HDMI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
$ xrandr | grep -i hdmi
HDMI-1 disconnected (normal left inverted right x axis y axis)
This is even when the monitor is connected.
IIRC it has never worked with nouveau, but on the other hand nvidia-340
is unsupported nowadays by Nvidia.
ProblemType: Bug
DistroRelease: Ubun
** Description changed:
- I tried both nouveau and nvidia-340 deivers. It used to work at least by
+ I tried both nouveau and nvidia-340 drivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
- $ xrandr
+ $ xrandr
xran
There exists no /etc/X11/xorg.conf file. I already switched to nouveau
using "Software & Updates" rebooted, switched back to nvidia-340 by the
same application, and rebooted, but it did not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I tried both nouveau and nvidia-340 deivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, current 1920 x 1200
The bug is in Scintilla widget:
https://github.com/geany/geany/issues/2502#issuecomment-939463462
Sadly, Ubuntu has an old version of it.
** Bug watch added: github.com/geany/geany/issues #2502
https://github.com/geany/geany/issues/2502
--
You received this bug notification because you are a
The package available in the PPA fixed the issue.
** Description changed:
[Impact]
- * Using monospace fonts, some parts of the glyphs might not be visible
-(this is especially evident using some monospsace fonts, there the
-underscore is not visible).
+ * Using monospace fonts, so
Actually this bug report is not about updates stopping working. This is
about not being able to remove a kernel with related packages completely
by usual ways due to a specific reason, if /boot becomes full enough.
There are other bug reports that call for bigger /boot partition or an
automatic way
** Bug watch added: github.com/mvo5/unattended-upgrades/issues #302
https://github.com/mvo5/unattended-upgrades/issues/302
** Also affects: unattended-upgrades via
https://github.com/mvo5/unattended-upgrades/issues/302
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
If user has linux-generic-hwe-18.04 installed, versioned linux-headers
packages depend on versioned linux-hwe-5.4-headers packages that will
not get removed. Consequently in time there will be hundreds of
thousands of unused files under /usr/src. For example I have about
45000
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Worked with nvidia-340 driver which is no more updated.
- When I resume, nothing works. Macbook keyboard lights are on, but
- otherwise the machine seems dead. Power button reboot needed.
+ Wh
Same thing in focal. I also tried 5.13.0-1010-oem kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922562
Title:
Resume from suspend to RAM fails
To manage notifications about this bug go to:
Please check out
https://help.ubuntu.com/community/ReportingBugs#Filing_a_general_bug_against_no_particular_package
(and the document in general). Please tell me the URL of the report
thereafter.
You told in #23 that you "Just ran in to this on Ubuntu 20.04", but to
be precise it is not even possi
Well, you could search for support in askubuntu.com. I think it may be a
bug that you have two flavors of kernels installed, if you did not
install the other manually. You might need to make a separate bug report
about that; removing the other flavor might be a workaround.
--
You received this bu
Hayden, did you try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage notifications about this bug go to:
ht
Remove the older generic kernel by linux-purge and then try booting the
respective oem kernel via advanced grub menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-im
Oh, the versions do not match. I do not see how removing the hwe kernels
would make it unbootable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package f
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New
** Tags added: focal
** Description changed:
Worked with nvidia-340 driver which is no more updated.
When I resume, nothing works. Macbook keyboard lights are on, but
otherwise the machine s
Hayden Clark, so you use "oem" kernels. If you do not need "generic"
kernels, you can save a lot of space in /boot by deleting all "generic"
kernels. Probably the easiest way to do it in your case is "sudo apt
autoremove linux-generic-hwe-20.04". Check that it does not remove any
"oem" kernels. If
I created the custom default.pa. It adds only two commands when compared to
default /etc/pulse/default.pa:
load-module module-native-protocol-tcp auth-ip-acl=192.168.100.51
set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo
The first one I need for network access of pulseaudio from a
** Attachment removed: "default.pa"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937919
Ti
From syslog:
"Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this
name or index.
Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize
daemon due to errors while executing startup commands. Source of commands:
/home/jarnos/.config/pulse//default.pa
From syslog:
"Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this
name or index.
Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize
daemon due to errors while executing startup commands. Source of commands:
/home/jarnos/.config/pulse//default.pa
** Description changed:
- First pulseaudio fails for some reason.
+ First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the
+ volume control in Xfce panel shows mute after I start session, but I can
+ not change it. This does not happen every time.
ProblemType: Bug
DistroRelease:
Could you attach output of "linux-purge --info"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage notificati
Did you run "sudo linux-purge --keep=1"? (or replace "1" by "0" to purge
even more)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513397/+files/syslog
** Description changed:
- This is not always reproduceable.
+ First pulseaudio fails for some reason.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package
Public bug reported:
This is not always reproduceable.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
Audio
** Description changed:
+ I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo"
+ in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this
+ version. I removed the line and run pulseaudio.
+
Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 C
** Description changed:
Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition
Audio Controller (rev 04)
+
+ EDIT: oh, it works again. I'll keep track of this issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1
Public bug reported:
Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition
Audio Controller (rev 04)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname:
Did you upgrade from older release or are the files generated when you
were using 20.04? Can you provide any logs concerning the issue? Do the
extra initrd.img* files match /boot/initrd.img-*.old-dkms, see
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513 ? Or do you
still have the respec
** Bug watch added: github.com/hexchat/hexchat/issues #2449
https://github.com/hexchat/hexchat/issues/2449
** Also affects: hexchat-irc via
https://github.com/hexchat/hexchat/issues/2449
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a m
You do not need to switch from guest session to do those nowadays:
https://help.ubuntu.com/community/CustomizeGuestSession
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022858
Title:
Guest session
*** This bug is a duplicate of bug 1022858 ***
https://bugs.launchpad.net/bugs/1022858
** This bug has been marked a duplicate of bug 1022858
Guest session asks for a password after switching users
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Does one need to switch from guest session? Maybe it should be disabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022858
Title:
Guest session asks for a password after switching users
To mana
** Description changed:
$ time apt-mark showauto >/dev/null
real 0m0,620s
user 0m0,557s
sys 0m0,052s
When I run the command first time, it is even much slower.
- I could do the job* in fraction of a time using awk in POSIX shell script
- (name it ./apt-mark-showauto.sh):
+ I
Public bug reported:
Worked with nvidia-340 driver which is no more updated.
When I resume, nothing works. Macbook keyboard lights are on, but
otherwise the machine seems dead. Power button reboot needed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-video-nouveau-hwe-18.04
@Sushenjit did you file a bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481804
Title:
LightDM's guest-account script should disable screen lock universally
for guest sessions
To mana
I tried the apt provided by focal-proposed. At least
sudo apt-get update -eany
gave exit status 100, if I disabled networking. Without -eany it gave 0.
I got the source code by 'apt source'.
I could not run test-apt-update-failure-propagation:
$ sudo ./apt-2.0.5/test/integration/test-apt-update-f
** Description changed:
$ time apt-mark showauto >/dev/null
- real 0m0.587s
- user 0m0.552s
- sys 0m0.016s
+ real 0m0,620s
+ user 0m0,557s
+ sys 0m0,052s
When I run the command first time, it is even much slower.
- I could do the job in fraction of a time using awk in POSIX sh
Good, besides simple text file format is easy to parse and check by command
line tools, if needed.
To my surprise, I have more manually installed packages than automatically
installed ones, so listing manually installed instead of automatically
installed in the file would not give benefit.
'apt
Well, Boolean algebra may have had some influence on that. It is a
common practice. 1 is shorter than yes.
Oh that is sad, because I am not satisfied with the speed of apt-mark.
On the other hand it is good. Another format or data structure may be
more efficient.
--
You received this bug notific
Public bug reported:
If I have Monospace 9 (default?) as the font in HexChat settings I can
not see underscore character '_' in the feed, but if I set it Monospace
10 and set Custom DPI setting in Xfce's Appearance dialog to 94 or
smaller, I see the character.
ProblemType: Bug
DistroRelease: Ubun
Oh, currently missing Auto-Installed field seems to mean the package is
manually installed even if the Package field exists. I suppose I can
rely on that in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Julian, BTW can you tell which version of apt was the latest where value
of the Auto-Installed field can be something else than 1 in the file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713219
Tit
Oh, actually I was already using set substraction in my code, but I was
also checking for 'Auto-Installed: 0'. Maybe that is necessary with some
older version of apt? (There was some bug in my code and that is why it
did not work correctly for some packages.) Sorry for blaming and
confusing. Howeve
Well, the script in the description is a bit too simple. In my
application, I was looking for 'Auto-Installed:' field with value 0 to
find manually installed packages, and due to the change in the way the
file is build nowadays I do not find them by the code anymore. Now the
field is pointless. I s
I wonder why didn't you choose to have only manually installed packages
in the file? It would be even smaller file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713219
Title:
'apt-mark showauto' a
So the file should only list packages that are installed automatically
or what?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713219
Title:
'apt-mark showauto' and 'apt show' is slow
To manage not
Maybe so, but the fact is that the file does not contain information
about all packages installed to my system. (apt 2.0.4 (amd64) / Ubuntu
20.04)
$ grep -c '^Package:' /var/lib/apt/extended_states
698
$ dpkg -l | grep ^ii | wc -l
1893
My file contains only records for packages that are automatic
Maybe I should make another bug report about it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713219
Title:
'apt-mark showauto' and 'apt show' is slow
To manage notifications about this bug go to
I just found out information about packages installed from PPAs are not found
in file configured in Dir::State::extended_states, so my script does not work
for them.
Are they found in some other file then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
mlocate does not seem to be included in Ubuntu 20.04 by default, but is
included in Xubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190696
Title:
updatedb.mlocate uses 100% of the hdd
Public bug reported:
There are applications bind to super+digit shortcuts in xfce4-keyboard-
settings. E.g. Super+2 = pidgin. There shortcuts seem random and user
may have better use for such shortcuts so better leave them alone.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xfce4-setting
** Changed in: xscreensaver (Ubuntu)
Status: New => Opinion
** Description changed:
+ EDIT: Now if it is generally so that when you lock by xscreensaver
+ before suspending, suspending happens only after fading has completed, I
+ withdraw this bug report.
+
Steps to reproduce
1. Run '
Despite the fact that 'xscreensaver-command -lock' may exit before it has faded
screen out in 'xscreensaver-command -lock https://bugs.launchpad.net/bugs/1858027
Title:
xscreensaver-command -lock finishes before desktop is invisible
To manage notifications about this bug go to:
https://bugs.la
** Description changed:
Steps to reproduce
1. Run 'xscreensaver-demo -prefs', activate the daemon, if requested
2. Ensure that "Fade to Black when Blanking" is set up with some non-zero
duration.
3. in terminal, run
xscreensaver-command -lock /dev/null && paplay
/usr/share/sounds/freed
** Description changed:
Steps to reproduce
1. Run 'xscreensaver-demo -prefs', activate the daemon, if requested
2. Ensure that "Fade to Black when Blanking" is set up with some non-zero
duration.
3. in terminal, run
xscreensaver-command -lock /dev/null && paplay
/usr/share/sounds/freed
1 - 100 of 2404 matches
Mail list logo
