Bug#1042414: gitlab: Sidekiq not working after 16 upgrade
Package: gitlab Version: 16.0.7+ds1-3~fto12+2 Severity: important X-Debbugs-Cc: er_ma...@darkbolt.net Dear Maintainer, Hi, After updating gitlab 15.7 to 16.0, sidekiq is not starting, not allowing apt installation to end correctly. On the same moment I've do a release change from old stable. On sidekiq log file I can find this: /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/definition.rb:36:in `build': /etc/Gemfile not found (Bundler::GemfileNotFound) from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler.rb:208:in `definition' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler.rb:156:in `setup' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/setup.rb:20:in `block in ' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/ui/shell.rb:136:in `with_level' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/ui/shell.rb:88:in `silence' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/setup.rb:20:in `' from :85:in `require' from :85:in `require' from /usr/share/gitlab/config/bundler_setup.rb:24:in `' from /usr/share/gitlab/sidekiq_cluster/cli.rb:3:in `require_relative' from /usr/share/gitlab/sidekiq_cluster/cli.rb:3:in `' from /usr/share/gitlab/bin/sidekiq-cluster:4:in `require_relative' from /usr/share/gitlab/bin/sidekiq-cluster:4:in `' Package gitlab-apt-pin-preferences are installed on the latest version before doing the apt-get upgrade and apt-get install gitlab. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-16-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor 2.0.18-2 ii bc 1.07.1-3+b1 ii bundler 2.3.15-2 ii bzip2 1.0.8-5+b1 ii dbconfig-pgsql 2.0.24 ii debconf [debconf-2.0] 1.5.82 ii exim4-daemon-light [mail-transport-age 4.96-15+deb12u1 nt] ii fonts-font-awesome [node-font-awesome] 5.0.10+really4.7.0~dfsg-4.1 ii gitlab-common 16.0.7+ds1-2~bpo12+1 ii gitlab-workhorse16.0.7+ds1-3~fto12+2 ii katex [node-katex] 0.16.4+~cs6.1.0-1 ii libjs-bootstrap4 [node-bootstrap] 4.6.1+dfsg1-4 ii libjs-pdf [node-pdfjs-dist] 2.14.305+dfsg-2 ii libjs-popper.js [node-popper.js]1.16.1+ds-6 ii libruby3.1 [ruby-rexml] 3.1.2-7 ii libssl-dev 3.0.9-1 ii lsb-base11.6 ii nginx [httpd] 1.22.1-9 ii node-autosize 4.0.4~dfsg1+~4.0.0-2 ii node-axios 1.2.1+dfsg-1 ii node-babel-loader 9.1.0-3 ii node-babel-plugin-lodash3.3.4+~cs2.0.1-6 ii node-babel7 7.20.15+ds1+~cs214.269.168-3 ii node-brace-expansion2.0.1-2 ii node-cache-loader 4.1.0+~cs2.0.0-4 ii node-clipboard 2.0.11+ds+~cs9.6.11-1 ii node-compression-webpack-plugin 10.0.0-2 ii node-copy-webpack-plugin11.0.0-3 ii node-core-js3.26.1-3 ii node-core-js-compat 3.26.1-3 ii node-core-js-pure 3.26.1-3 ii node-cron-validator 1.3.1-3 ii node-css-loader 6.7.2+~cs14.0.11-1 ii node-d3 5.16.0-10 ii node-d3-selection 1.4.0-8 ii node-dateformat 5.0.3-5 ii node-dompurify 2.4.1+dfsg+~2.4.0-1 ii node-exports-loader 4.0.0-1 ii node-file-loader6.2.0-3 ii node-fuzzaldrin-plus0.6.0+dfsg+~0.6.2-3 ii node-glob 8.0.3+~cs8.4.15-1 ii node-imports-loader 0.8.0-6 ii node-jed1.1.1-4 ii node-jquery 3.6.1+dfsg+~3.5.14-1 ii node-jquery-ujs 1.2.3-2 ii node-js-cookie 3.0.1+~3.0.0-3 ii node-js-yaml4.1.0+dfsg+~4.0.5-7 ii node-jszip 3.10.1+dfsg-1 ii node-jszip-utils0.1.0+dfsg-1 ii
Bug#975493: gitlab: Gitlab install script not working
Package: gitlab Version: 13.3.9-1+fto10+1 Severity: important Hi, Gitlab are not installing. I doesn't know the reason, but when I try to install it through apt-get upgrade (following debian/gitlab page for upgrading), that's not working. The log are the following: Precompiling assets... fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git Attention: used pure ruby version of MurmurHash3 /usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant Gitlab::COM_URL /usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was here /usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant Gitlab::STAGING_COM_URL /usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of STAGING_COM_URL was here /usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant Gitlab::APP_DIRS_PATTERN /usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of APP_DIRS_PATTERN was here /usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant Gitlab::SUBDOMAIN_REGEX /usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of SUBDOMAIN_REGEX was here /usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant Gitlab::VERSION /usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of VERSION was here /usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant Gitlab::INSTALLATION_TYPE /usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of INSTALLATION_TYPE was here /usr/share/gitlab/lib/gitlab.rb:44: warning: already initialized constant Gitlab::HTTP_PROXY_ENV_VARS /usr/share/gitlab/lib/gitlab.rb:44: warning: previous definition of HTTP_PROXY_ENV_VARS was here yarn install v1.22.4 [1/4] Resolving packages... success Already up-to-date. $ node ./scripts/frontend/postinstall.js success Dependency postinstall check passed. Done in 0.74s. WARNING on line 297, column 11 of /usr/share/gitlab/app/assets/stylesheets/framework/common.scss: Compound selectors may no longer be extended. Consider `@extend .card, .card-body` instead. See http://bit.ly/ExtendCompound for details. WARNING on line 208, column 13 of /usr/share/gitlab/app/assets/stylesheets/framework/filters.scss: Compound selectors may no longer be extended. Consider `@extend .form-control, :hover` instead. See http://bit.ly/ExtendCompound for details. DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#292961 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#4b4ba3 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#1a3652 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#2261a1 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#0d4524 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#156b39 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#691a16 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#a62e21 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead.
Bug#956205: gitlab: Problem installing 12.8.8-6
Package: gitlab
Version: 12.8.8-6+fto10+1
Severity: grave
Justification: renders package unusable
Hi,
Gitlab 12.8.8 installation fails.
Log:
Bundle complete! 198 Gemfile dependencies, 362 gems now installed.
Gems in the groups development and test were not installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Running final rake tasks and tweaks...
gitlab_production database is not empty, skipping gitlab setup
Precompiling assets...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Attention: used pure ruby version of MurmurHash3
/usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant
Gitlab::COM_URL
/usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was
here
/usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant
Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant
Gitlab::SUBDOMAIN_REGEX
/usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of
SUBDOMAIN_REGEX was here
/usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant
Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of VERSION was
here
/usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant
Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant
Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of
HTTP_PROXY_ENV_VARS was here
yarn install v1.22.4
[1/4] Resolving packages...
success Already up-to-date.
$ node ./scripts/frontend/postinstall.js
success Dependency postinstall check passed.
Done in 1.45s.
rake aborted!
SassC::SyntaxError: Error: Top-level selectors may not contain the parent
selector "&".
on line 6:9 of node_modules/@gitlab/ui/src/scss/components.scss
from line 13:9 of node_modules/@gitlab/ui/src/scss/gitlab_ui.scss
from line 5:9 of app/assets/stylesheets/framework.scss
from line 19:9 of app/assets/stylesheets/application.scss
>> &.gl-avatar-identicon-bg#{$i} {
--^
/usr/share/gitlab/node_modules/@gitlab/ui/src/scss/../components/base/avatar/avatar.scss:82
/usr/share/rubygems-integration/all/gems/sassc-2.2.1/lib/sassc/engine.rb:49:in
`render'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
installed gitlab package post-installation script subprocess returned error
exit status 1
Thanks,
-- System Information:
Debian Release: bullseye/sid
APT prefers buster-fasttrack
APT policy: (500, 'buster-fasttrack'), (500, 'buster-backports'), (500,
'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitlab depends on:
ii asciidoctor 2.0.10-2
ii bc 1.07.1-2+b2
ii bundler 2.1.4-1
ii bzip2 1.0.8-2
ii dbconfig-pgsql 2.0.13
ii debconf [debconf-2.0] 1.5.73
ii exim4-daemon-light [mail-transport-agent] 4.93-13
ii gitlab-common 12.8.8-6+fto10+1
ii gitlab-workhorse8.30+debian-1
ii libjs-bootstrap4 [node-bootstrap] 4.4.1+dfsg1-2
ii libjs-popper.js [node-popper.js]1.16.0+ds2-1
ii libjs-uglify2.8.29-6
ii lsb-base11.1.0
ii nginx 1.16.1-3
ii nginx-full [nginx] 1.16.1-3
ii node-autosize 4.0.2~dfsg1-3
ii node-axios 0.19.0+dfsg-2
ii node-brace-expansion1.1.11-1
ii node-cache-loader 2.0.1-2
ii node-chart.js 2.9.3+dfsg-2
ii node-clipboard 2.0.6+ds-1
ii node-core-js3.6.1-3
ii node-css-loader 1.0.1+repack-1
ii node-d3
Bug#949591: gitlab: Gitlab not serving cached assets
Package: gitlab Version: 12.6.4-1+fto10+1 Severity: minor Apparently, gitlab is not serving cached assets. That's result on a very long loading time. Example of most relevant file: Cached: 304 Not Modified https://salsa.debian.org/assets/webpack/main.b91d0a07.chunk.js <-- 2,55mb, 849ms load time 304 Not Modified https://assets.gitlab-static.net/assets/webpack/main.45f98342.chunk.js <-- 0b, 42ms load time My installation: 200 OK https://git.myserver.net/assets/webpack/main.chunk.js <-- 20.87mb, 12135ms load time First of all, the name it's different. On Salsa and gitlab.org, file have a hash in the name. Second, on my install, always response 200 OK. Pages are served from nginx. Other resources are served OK but the name also doesn't have these hash. Example: 304 Not Modified https://git.myserver.net/assets/webpack/runtime.bundle.js <-- 0b, 308ms load time. What's the problem with that file? -- System Information: Debian Release: bullseye/sid APT prefers buster-fasttrack APT policy: (500, 'buster-fasttrack'), (500, 'buster-backports'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab depends on: ii asciidoctor 2.0.10-2 ii bc 1.07.1-2+b2 ii bundler 1.17.3-3 ii bzip21.0.8-2 ii dbconfig-pgsql 2.0.13 ii debconf [debconf-2.0]1.5.73 ii exim4-daemon-light [mail-transport-agent]4.93-9 ii gitlab-common12.6.4-1+fto10+1 ii gitlab-workhorse 8.18.0+debian-1 ii libjs-bootstrap4 [node-bootstrap]4.4.1+dfsg1-1 ii libjs-pdf1.5.188+dfsg-1~bpo10+1 ii libjs-popper.js [node-popper.js] 1.16.0+ds2-1 ii libjs-uglify 2.8.29-6 ii lsb-base 11.1.0 ii nginx1.16.1-3 ii nginx-full [nginx] 1.16.1-3 ii node-autosize4.0.2~dfsg1-3 ii node-axios 0.19.0+dfsg-2 ii node-brace-expansion 1.1.11-1 ii node-cache-loader2.0.1-2 ii node-chart.js2.9.3+dfsg-2 ii node-core-js 3.6.1-2 ii node-css-loader 1.0.1-1 ii node-d3 5.12.0-1~bpo10+1 ii node-d3-array1.2.4-2 ii node-d3-axis 1.0.12-2 ii node-d3-brush1.1.5-1 ii node-d3-ease 1.0.5-2 ii node-d3-scale2.2.2-1~bpo10+1 ii node-d3-selection1.4.0-5 ii node-d3-shape1.3.5-2 ii node-d3-time 1.0.11-3 ii node-d3-time-format 2.1.3-2 ii node-d3-transition 1.2.0-4 ii node-dateformat 3.0.0-1 ii node-exports-loader 0.7.0-2 ii node-file-loader 3.0.1-1 ii node-fuzzaldrin-plus 0.5.0+dfsg-3 ii node-glob7.1.6-1 ii node-imports-loader 0.8.0-2 ii node-jed 1.1.1-1 ii node-jquery 3.4.0+dfsg-1 ii node-jquery-ujs 1.2.2-2 ii node-jquery.waitforimages2.4.0+ds-1 ii node-js-cookie 2.2.1-1 ii node-jszip 3.2.2+dfsg-2~bpo10+1 ii node-jszip-utils 0.0.2+dfsg-1 ii node-marked 0.5.1+dfsg-1 ii node-mousetrap 1.6.1+ds-1 ii node-raven-js3.22.1+dfsg-2 ii node-raw-loader 1.0.0-2 ii node-three-orbit-controls82.1.0-2 ii node-three-stl-loader1.0.6-2 ii
Bug#947754: [omv.dynamicpuzzle.ro] gitlab mattermost integration error
Package: gitlab
Version: 12.6.2-2+fto10+1
Followup-For: Bug #947754
Hi,
I've updated to 12.6.2.2 but bug is still present.
I can view a difference on the request from 12.5.4 version:
Processing by Oauth::AuthorizationsController#new as HTML
Parameters: {"response_type"=>"code", "client_id"=>"",
"redirect_uri"=>"https:///oauth2/callback/gitlab",
"state"=>""}
(These two lines are not present on the log in 12.5.4)
Log from 12.6.2, trying to use oauth from my on-premises sonarqube.
Started GET
"/oauth/authorize?response_type=code_id=_uri=https%3A%2F%2F%2Foauth2%2Fcallback%2Fgitlab="
for x.x.x.x at 2020-01-10 02:51:01 +0100
Processing by Gitlab::RequestForgeryProtection::Controller#index as HTML
Parameters: {"response_type"=>"code", "client_id"=>"",
"redirect_uri"=>"https:///oauth2/callback/gitlab",
"state"=>""}
Completed 200 OK in 1ms (ActiveRecord: 0.0ms | Elasticsearch: 0.0ms)
Processing by Oauth::AuthorizationsController#new as HTML
Parameters: {"response_type"=>"code", "client_id"=>"",
"redirect_uri"=>"https:///oauth2/callback/gitlab",
"state"=>""}
Completed 500 Internal Server Error in 5ms (ActiveRecord: 0.0ms |
Elasticsearch: 0.0ms)
NoMethodError (undefined method `mapping' for Doorkeeper::Rails::Routes:Class):
lib/gitlab/request_profiler/middleware.rb:17:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/correlation_id.rb:16:in `block in call'
lib/gitlab/middleware/correlation_id.rb:15:in `call'
lib/gitlab/middleware/multipart.rb:117:in `call'
lib/gitlab/middleware/read_only/controller.rb:48:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:32:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:49:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'
I've only updated system (apt-get upgrade && apt-get dist-upgrade), for update
gitlab and required gems and other apps on the system. I didn't change any
configuration on gitlab nor sonarqube. Token / appID are the ones generated on
the past.
Maybe there's another check I can do about this problem? I didn't try with my
on-premises sentry (they fails also on 12.5.4, check previous reports on this
bug).
-- System Information:
Debian Release: bullseye/sid
APT prefers buster-fasttrack
APT policy: (500, 'buster-fasttrack'), (500, 'buster-backports'), (500,
'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitlab depends on:
ii asciidoctor 2.0.10-2
ii bc 1.07.1-2+b2
ii bundler 1.17.3-3
ii bzip2 1.0.8-2
ii dbconfig-pgsql 2.0.13
ii debconf [debconf-2.0] 1.5.73
ii exim4-daemon-light [mail-transport-agent] 4.93-5
ii gitlab-common 12.6.2-2+fto10+1
ii gitlab-workhorse8.18.0+debian-1~bpo10+1
ii libjs-bootstrap4 [node-bootstrap] 4.4.1+dfsg1-1
ii libjs-pdf 1.5.188+dfsg-1~bpo10+1
ii libjs-popper.js [node-popper.js]1.16.0+ds2-1
ii libjs-uglify2.8.29-6
ii lsb-base11.1.0
ii nginx 1.16.1-2
ii nginx-full [nginx] 1.16.1-2
ii node-autosize 4.0.2~dfsg1-3
ii node-axios 0.19.0+dfsg-2
ii node-brace-expansion1.1.8-1
ii node-cache-loader 2.0.1-2
ii node-chart.js 2.9.3+dfsg-2
ii node-core-js2.4.1-2
ii node-css-loader 1.0.1-1
ii node-d3 5.12.0-1~bpo10+1
ii node-d3-array 1.2.4-2
ii node-d3-axis1.0.12-2
ii node-d3-brush 1.1.5-1
ii node-d3-ease1.0.5-2
ii node-d3-scale 2.2.2-1~bpo10+1
ii node-d3-selection 1.4.0-5
ii node-d3-shape 1.3.5-2
ii node-d3-time1.0.11-3
ii
Bug#947754: [omv.dynamicpuzzle.ro] gitlab mattermost integration error
Package: gitlab
Version: 12.5.4-2+fto10+1
Followup-For: Bug #947754
Another case with the error, but in this case is not for use oauth directly,
nor for sentry server integration.
(Anyways, apparently Sentry it's trying to do an oauth authentication before
starting process, it's the same error apparently.
This case are only tested on 12.5.4
Started GET
"/oauth/authorize?scope=api=_uri=https%3A%2F%2F>sentry.fqdn>%2Fextensions%2Fgitlab%2Fsetup%2F_type=code_id="
for x.x.x.x at 2020-01-01 05:32:14 +0100
Processing by Oauth::AuthorizationsController#new as HTML
Parameters: {"scope"=>"api", "state"=>"",
"redirect_uri"=>"https:///extensions/gitlab/setup/",
"response_type"=>"code", "client_id"=>""}
Completed 500 Internal Server Error in 5ms (ActiveRecord: 0.5ms |
Elasticsearch: 0.0ms)
NoMethodError (undefined method `mapping' for Doorkeeper::Rails::Routes:Class):
lib/gitlab/request_profiler/middleware.rb:17:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/correlation_id.rb:16:in `block in call'
lib/gitlab/middleware/correlation_id.rb:15:in `call'
lib/gitlab/middleware/multipart.rb:117:in `call'
lib/gitlab/middleware/read_only/controller.rb:48:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:32:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:49:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'
Bug#947754: gitlab: Gitlab oauth problem (Was: mattermost integration error)
Package: gitlab
Version: 12.5.4-2+fto10+1
Followup-For: Bug #947754
A try to connect sonarqube with gitlab via oAuth fails with the same error.
Apparently, the problem are the oauth itself.
Bug is present, at lest, since 12.2.9. I didn't remember if it's present on
12.0.9 or 12.1.14.
Started POST "/api/v4/jobs/request" for ::1 at 2019-12-31 16:09:33 +0100
Started GET
"/oauth/authorize?response_type=code_id=_uri=https%3A%2F%2F%2Foauth2%2Fcallback%2Fgitlab="
for x.x.x.x at 2019-12-31 16:09:34 +0100
Processing by Oauth::AuthorizationsController#new as HTML
Parameters: {"response_type"=>"code", "client_id"=>"",
"redirect_uri"=>"https:///oauth2/callback/gitlab",
"state"=>""}
Completed 500 Internal Server Error in 9ms (ActiveRecord: 0.4ms |
Elasticsearch: 0.0ms)
NoMethodError (undefined method `mapping' for Doorkeeper::Rails::Routes:Class):
lib/gitlab/request_profiler/middleware.rb:17:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/correlation_id.rb:16:in `block in call'
lib/gitlab/middleware/correlation_id.rb:15:in `call'
lib/gitlab/middleware/multipart.rb:117:in `call'
lib/gitlab/middleware/read_only/controller.rb:48:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:32:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:49:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'
Started POST "/api/v4/jobs/request" for ::1 at 2019-12-31 16:09:36 +0100
-- System Information:
Debian Release: bullseye/sid
APT prefers buster-fasttrack
APT policy: (500, 'buster-fasttrack'), (500, 'buster-backports'), (500,
'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitlab depends on:
ii asciidoctor 2.0.10-2
ii bc 1.07.1-2+b2
ii bundler 1.17.3-3
ii bzip21.0.8-2
ii dbconfig-pgsql 2.0.13
ii debconf [debconf-2.0]1.5.73
ii exim4-daemon-light [mail-transport-agent]4.92.3-1
ii gitlab-common12.5.4-2+fto10+1
ii gitlab-workhorse 8.16.0+debian-1
ii libjs-bootstrap4 [node-bootstrap]4.4.1+dfsg1-1
ii libjs-pdf1.5.188+dfsg-1~bpo10+1
ii libjs-popper.js [node-popper.js] 1.16.0+ds2-1
ii libjs-uglify 2.8.29-6
ii lsb-base 11.1.0
ii nginx1.16.1-2
ii nginx-full [nginx] 1.16.1-2
ii node-autosize4.0.2~dfsg1-3
ii node-axios 0.19.0+dfsg-2
ii node-brace-expansion 1.1.8-1
ii node-cache-loader2.0.1-2
ii node-chart.js2.9.3+dfsg-2
ii node-core-js 2.4.1-2
ii node-css-loader 1.0.1-1
ii node-d3 5.12.0-1~bpo10+1
ii node-d3-array1.2.4-2
ii node-d3-axis 1.0.12-2
ii node-d3-brush1.1.5-1
ii node-d3-ease 1.0.5-2
ii node-d3-scale2.2.2-1~bpo10+1
ii node-d3-selection1.4.0-5
ii node-d3-shape1.3.5-2
ii node-d3-time 1.0.11-3
ii node-d3-time-format 2.1.3-2
ii node-d3-transition 1.2.0-4
ii node-dateformat 3.0.0-1
ii node-exports-loader 0.7.0-2
ii node-file-loader 3.0.1-1
ii node-fuzzaldrin-plus 0.5.0+dfsg-3
ii node-glob7.1.6-1
ii node-imports-loader 0.8.0-2
ii node-jed 1.1.1-1
ii node-jquery 3.4.0+dfsg-1
ii node-jquery-ujs
Bug#944596: gitlab: Upgrading to 12.2.9-1 fails
Package: gitlab
Version: 12.2.9-1+fto10+1
Followup-For: Bug #944596
More info about the bug:
- Deleting file active_record_mysql_timestamp.rb, fails on
active_record_mysql_timestamp.rb, because the same error, "undefined method
mysql?".
Error MSG:
NoMethodError: undefined method `mysql?' for Gitlab::Database:Module
/usr/share/gitlab/config/initializers/ar_mysql_jsonb_support.rb:9:in `'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in
`load'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in
`block in load'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in
`load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in
`load'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:657:in
`block in load_config_initializer'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in
`instrument'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:656:in
`load_config_initializer'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:614:in
`block (2 levels) in '
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:613:in
`each'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:613:in
`block in '
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:32:in
`instance_exec'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:32:in
`run'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:61:in
`block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:50:in
`each'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:50:in
`tsort_each_child'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:60:in
`run_initializers'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:361:in
`initialize!'
/usr/share/gitlab/config/environment.rb:6:in `'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
`require'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
`block in require'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in
`load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
`require'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:337:in
`require_environment!'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:520:in
`block in run_tasks_blocks'
Tasks: TOP => db:migrate => db:load_config => environment
Deleting this file too, continue on db:migrate task, but this one fails too.
Error MSG:
(some output ommited)
== 20190723105753 AddIndexOnIdentitiesLowerExternUidAndProvider: migrating
-- transaction_open?()
-> 0.s
-- index_exists?(:identities, "lower(extern_uid), provider",
{:name=>"index_on_identities_lower_extern_uid_and_provider",
:algorithm=>:concurrently})
-> 0.0033s
-- execute("SET statement_timeout TO 0")
-> 0.0005s
-- add_index(:identities, "lower(extern_uid), provider",
{:name=>"index_on_identities_lower_extern_uid_and_provider",
:algorithm=>:concurrently})
-- execute("RESET ALL")
-> 0.0004s
rake aborted!
StandardError: An error has occurred, all later migrations canceled:
PG::UndefinedColumn: ERROR: column "lower(extern_uid), provider" does not exist
: CREATE INDEX CONCURRENTLY
"index_on_identities_lower_extern_uid_and_provider" ON "identities"
("lower(extern_uid), provider" )
/usr/share/rubygems-integration/all/gems/activerecord-5.2.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:75:in
`async_exec'
/usr/share/rubygems-integration/all/gems/activerecord-5.2.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:75:in
`block (2 levels) in execute'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:48:in
`block in permit_concurrent_loads'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/concurrency/share_lock.rb:187:in
`yield_shares'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:47:in
`permit_concurrent_loads'
/usr/share/rubygems-integration/all/gems/activerecord-5.2.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:74:in
`block in execute'
Bug#944596: gitlab: Upgrading to 12.2.9-1 fails
Package: gitlab Version: 12.2.9-1+fto10+1 Followup-For: Bug #944596 Hi, I have exactly the same problem. Installation are originally on gitlab 8, until yesterday working without problem on 12.1 NoMethodError: undefined method `mysql?' for Gitlab::Database:Module /usr/share/gitlab/config/initializers/active_record_mysql_timestamp.rb:7:in `' Tasks: TOP => db:migrate => db:load_config => environment Maybe this file needs to be deleted...? -- System Information: Debian Release: bullseye/sid APT prefers buster-fasttrack APT policy: (500, 'buster-fasttrack'), (500, 'buster-backports'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab depends on: ii asciidoctor 2.0.10-2 ii bc 1.07.1-2+b2 ii bundler 1.17.3-3 ii bzip21.0.8-2 ii dbconfig-pgsql 2.0.13 ii debconf [debconf-2.0]1.5.73 ii exim4-daemon-light [mail-transport-agent]4.92.3-1 ii gitlab-common12.2.9-1+fto10+1 ii gitlab-workhorse 8.8.1+debian-1~bpo10+1 ii libjs-bootstrap4 [node-bootstrap]4.3.1+dfsg2-4 ii libjs-pdf1.5.188+dfsg-1~bpo10+1 ii libjs-popper.js [node-popper.js] 1.14.6+ds2-2 ii libjs-uglify 2.8.29-6 ii lsb-base 11.1.0 ii nginx1.16.1-2 ii nginx-full [nginx] 1.16.1-2 ii node-autosize4.0.2~dfsg1-3 ii node-axios 0.19.0+dfsg-2 ii node-brace-expansion 1.1.8-1 ii node-cache-loader2.0.1-2 ii node-chart.js2.7.3+dfsg-5 ii node-core-js 2.4.1-2 ii node-css-loader 1.0.1-1 ii node-d3 4.13.0-10 ii node-d3-array1.2.4-2 ii node-d3-axis 1.0.12-2 ii node-d3-brush1.0.6-3 ii node-d3-ease 1.0.5-2 ii node-d3-scale1.0.7-6 ii node-d3-selection1.4.0-5 ii node-d3-shape1.3.5-2 ii node-d3-time 1.0.11-3 ii node-d3-time-format 2.1.3-2 ii node-d3-transition 1.2.0-4 ii node-dateformat 3.0.0-1 ii node-exports-loader 0.7.0-2 ii node-file-loader 3.0.1-1 ii node-fuzzaldrin-plus 0.5.0+dfsg-3 ii node-glob7.1.3-2 ii node-imports-loader 0.8.0-2 ii node-jed 1.1.1-1 ii node-jquery 3.4.0+dfsg-1 ii node-jquery-ujs 1.2.2-2 ii node-jquery.waitforimages2.4.0+ds-1 ii node-js-cookie 2.2.0-2 ii node-jszip 3.2.2+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-1 ii node-mousetrap 1.6.1+ds-1 ii node-pikaday 1.8.0-1 ii node-raven-js3.22.1+dfsg-2 ii node-raw-loader 1.0.0-2 ii node-three-orbit-controls82.1.0-2 ii node-three-stl-loader1.0.6-2 ii node-timeago.js 3.0.2+dfsg-5 ii node-underscore 1.9.1~dfsg-1 ii node-url-loader 1.1.2-1 ii node-vue-resource1.5.1+dfsg-5 ii node-webpack-stats-plugin0.2.1-1 ii node-worker-loader 2.0.0-2 ii nodejs 10.17.0~dfsg-2 ii openssh-client
Bug#925606: gitlab: Fail to upgrade (error with activesupport gem)
Package: gitlab Version: 11.8.3-1+fto10+1 Severity: important Hi, Doing an apt-get upgrade fails to install gitlab (upgrading from 11.8.2). The error message are: Bundle complete! 187 Gemfile dependencies, 315 gems now installed. Gems in the groups development and test were not installed. Use `bundle info [gemname]` to see where a bundled gem is installed. Running final rake tasks and tweaks... gitlab_production database is not empty, skipping gitlab setup fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git rake aborted! LoadError: cannot load such file -- sprockets/rails/context /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `block in require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in `load_dependency' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `block in require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in `load_dependency' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `block in require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in `load_dependency' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `block in require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in `load_dependency' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:81:in `block (2 levels) in require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in `each' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in `block in require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in `each' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in `require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler.rb:114:in `require' /usr/share/gitlab/config/application.rb:5:in `' /usr/share/gitlab/Rakefile:5:in `require' /usr/share/gitlab/Rakefile:5:in `' (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: gitlab E: Sub-process /usr/bin/dpkg returned an error code (1) Downgrading package to previous working version gives the same error. Thanks, -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab depends on: ii asciidoctor1.5.8-1 ii bc 1.07.1-2+b1 ii bundler1.17.3-3 ii bzip2 1.0.6-9 ii dbconfig-pgsql 2.0.11 ii debconf [debconf-2.0] 1.5.71 ii exim4-daemon-light [mail-transport-agent] 4.92-2 ii gitlab-common 11.8.3-1+fto10+1 ii gitlab-workhorse 7.6.0+debian-1+b20 ii libjs-uglify 2.8.29-6 ii lsb-base 10.2019031300 ii nginx 1.14.2-2 ii nginx-full [nginx] 1.14.2-2 ii nodejs 10.15.2~dfsg-1 ii openssh-client 1:7.9p1-9 ii postgresql-client 11+200 ii postgresql-client-10 [postgresql-client] 10.5-1 ii postgresql-client-11 [postgresql-client] 11.2-2 ii postgresql-contrib 11+200 ii rake 12.3.1-3 ii redis-server 5:5.0.3-4 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii
Bug#917084: gitlab: Gitlab - Letsencrypt not renewing correctly
Package: gitlab Version: 11.5.4+dfsg-1 Severity: normal Hi, I've detected certbot cannot renew gitlab certificate correctly. The certificate creation has been done by gitlab & certbot on the gitlab installation. Now, trying to renew certificate, certbot gives an error: - The following errors were reported by the server: Domain: git.example.com Type: unauthorized Detail: Invalid response from http://git.example.com/.well-known/acme-challenge/ovA3oeVF7G6Ju9oGumay12a6juyWVCrq8TJxyLpI5LQ: "\n\nhttp://ogp.me/ns#\;>\n\n pn ruby-flipper-active-support-cache-store ii ruby-flowdock 0.7.1-1 ii ruby-fog-aliyun0.2.0-1 ii ruby-fog-aws 2.0.1-1 ii ruby-fog-core 1.45.0-2 ii ruby-fog-google1.8.1-2 ii ruby-fog-local 0.3.0-1 ii ruby-fog-openstack 0.1.6-4 ii ruby-fog-rackspace 0.1.1-4 ii ruby-fogbugz 0.2.1-3 ii ruby-font-awesome-rails4.7.0.4-1 ii ruby-gemojione 3.3.0-1 ii ruby-gettext-i18n-rails1.8.0-1 ii ruby-gettext-i18n-rails-js 1.3.0+dfsg-2 pn ruby-gitaly-proto ii ruby-github-markup 1.7.0+dfsg-2 ii ruby-gitlab-sidekiq-fetcher0.3.0-1 ii ruby-gon 6.2.1-1 ii ruby-google-api-client 0.23.4-2 ii ruby-google-protobuf 3.6.1.3-1 ii ruby-gpgme 2.0.18-1 ii ruby-grape 1.1.0-1 ii ruby-grape-entity 0.7.1-1 ii ruby-grape-logging 1.7.0-1 ii ruby-grape-path-helpers1.0.6-1 ii ruby-graphiql-rails1.4.10-1 ii ruby-graphql 1.8.4-1 ii ruby-grpc 1.16.1-1 ii ruby-hamlit2.8.8-1 ii ruby-hangouts-chat 0.0.5-1 ii ruby-hashie-forbidden-attributes 0.1.1-1 ii ruby-health-check 2.6.0-1 ii ruby-hipchat 1.5.2-3 ii ruby-html-pipeline 2.8.4-1 ii ruby-html2text 0.2.0-1 ii ruby-httparty 0.16.2+dfsg1-2 ii ruby-icalendar 2.4.1-2 ii ruby-influxdb 0.2.3-2 ii ruby-jira 1.5.0-1 ii ruby-jquery-atwho-rails1.3.2-2 ii ruby-js-regex 3.1.1-1 ii ruby-jwt 1.5.6-1 ii ruby-kaminari 1.0.1-4 ii ruby-kgio 2.11.2-1+b1 ii ruby-kubeclient3.1.2-1 ii ruby-licensee 8.9.2-1 ii ruby-lograge 0.10.0-1 ii ruby-loofah2.2.2-1 ii ruby-mail-room 0.9.1-2 ii ruby-method-source 0.9.2-1 ii ruby-mini-magick 4.8.0-2 ii ruby-net-ldap 0.16.1-1 ii ruby-net-ssh 1:5.0.2-2 ii ruby-nokogiri 1.8.4-1 ii ruby-ntlm 0.6.1-2 ii ruby-oauth21.4.0-3 ii ruby-octokit 4.12.0-1 ii ruby-omniauth 1.8.1-1 ii ruby-omniauth-auth02.0.0-1 ii ruby-omniauth-authentiq0.3.3-1 ii ruby-omniauth-azure-oauth2 0.0.9-2 ii ruby-omniauth-cas3 1.1.4-2 ii ruby-omniauth-crowd2.4.0-1 ii ruby-omniauth-facebook 4.0.0-2 ii ruby-omniauth-github 1.3.0-1 ii ruby-omniauth-gitlab 1.0.2-1 ii ruby-omniauth-google-oauth20.5.3-1 ii ruby-omniauth-kerberos 0.3.0-3 ii ruby-omniauth-ldap 2.0.4-2 ii ruby-omniauth-oauth2-generic 0.2.2-1 ii ruby-omniauth-saml 1.10.0-1 ii ruby-omniauth-shibboleth 1.3.0-1 ii ruby-omniauth-twitter 1.4.0-1 ii ruby-org 0.9.12-2 ii ruby-parser3.11.0-1 ii ruby-peek 1.0.1-1 ii ruby-peek-gc 0.0.2-1 ii ruby-peek-pg 1.3.0-1 ii ruby-peek-rblineprof 0.2.0-1 ii ruby-peek-redis1.2.0-1 ii ruby-pg
Bug#915136: Gitlab: Error 503 loading some projects
Package: gitlab
Version: 11.3.10+dfsg-2
Severity: important
Hi,
I'm working with Gitlab 11.3.10, and after a commit & push, I cannot see one of
my projects.
The error message are:
Started GET "/Group/Project/commits/master" for x.x.x.x at 2018-11-30 21:30:02
+0100
Processing by Projects::CommitsController#show as HTML
Parameters: {"namespace_id"=>"Group", "project_id"=>"Project", "id"=>"master"}
Gitlab::Git::CommandError (14:all SubConns are in TransientFailure):
lib/gitlab/git/repository.rb:1010:in `rescue in wrapped_gitaly_errors'
lib/gitlab/git/repository.rb:1003:in `wrapped_gitaly_errors'
lib/gitlab/git/repository.rb:364:in `log'
lib/gitlab/git/commit.rb:41:in `where'
app/models/repository.rb:145:in `commits'
app/controllers/projects/commits_controller.rb:63:in `set_commits'
lib/gitlab/i18n.rb:53:in `with_locale'
lib/gitlab/i18n.rb:59:in `with_user_locale'
app/controllers/application_controller.rb:405:in `set_locale'
lib/gitlab/middleware/multipart.rb:101:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:17:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/read_only/controller.rb:38:in `call'
lib/gitlab/middleware/read_only.rb:16:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
lib/gitlab/middleware/release_env.rb:10:in `call'
Completed 503 Service Unavailable in 600ms (Views: 277.3ms | ActiveRecord:
12.2ms)
Same problem appears loading:
- Project -> Details.
- Repository -> Files.
- Repository -> Commits.
- Repository -> Branches.
- Repository -> Tags.
- Repository -> Contributos.
- Repository -> Graph (with Error 2).
- Repository -> Charts.
Repository has been working without any problem until a last commit. The commit
are here:
commit 9827dcf92b7eccdac395697b650bc1ff0f3fadc7 (HEAD -> master, origin/master,
origin/HEAD)
Merge: a6a31bdea f2a6999a9
Author: author2
Date: Fri Nov 30 15:04:56 2018 +0100
Merge branch 'master' of git.example.com:Group/Project
commit a6a31bdea50006b4853b73e61c61bf971fc435b5
Author: author2
Date: Fri Nov 30 15:04:19 2018 +0100
Actualizados los plugins segun el repo
Git commands are working without problem. rake gitlab:check does not report any
problem. I've triggered repository check from admin interface, and none
improvement.
Upgrading to gitlab 11.3.11 does not resolve the problem.
Error 2:
Gitlab::Git::CommandError (14:all SubConns are in TransientFailure):
lib/gitlab/git/repository.rb:1010:in `rescue in wrapped_gitaly_errors'
lib/gitlab/git/repository.rb:1003:in `wrapped_gitaly_errors'
lib/gitlab/git/repository.rb:210:in `tags'
lib/gitlab/git/repository.rb:481:in `refs_hash'
app/models/repository.rb:486:in `method_missing'
lib/gitlab/git/commit.rb:398:in `refs'
lib/gitlab/git/commit.rb:294:in `ref_names'
app/models/network/commit.rb:17:in `method_missing'
app/models/network/graph.rb:134:in `include_ref?'
app/models/network/graph.rb:123:in `block in commits_sort_by_ref'
app/models/network/graph.rb:122:in `sort'
app/models/network/graph.rb:122:in `commits_sort_by_ref'
app/models/network/graph.rb:66:in `index_commits'
app/models/network/graph.rb:19:in `initialize'
app/controllers/projects/network_controller.rb:23:in `new'
app/controllers/projects/network_controller.rb:23:in `block (2 levels) in
show'
app/controllers/projects/network_controller.rb:15:in `show'
lib/gitlab/i18n.rb:53:in `with_locale'
lib/gitlab/i18n.rb:59:in `with_user_locale'
app/controllers/application_controller.rb:405:in `set_locale'
lib/gitlab/middleware/multipart.rb:101:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:17:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/read_only/controller.rb:38:in `call'
lib/gitlab/middleware/read_only.rb:16:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
lib/gitlab/middleware/release_env.rb:10:in `call'
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitlab depends on:
ii asciidoctor1.5.8-1
ii bc 1.07.1-2+b1
ii bundler1.16.1-3
ii bzip2 1.0.6-9
ii dbconfig-pgsql 2.0.10
ii debconf [debconf-2.0]
Bug#914496: gitlab-shell: Fail on gitlab-shell on git push
Package: gitlab-shell Version: 8.3.3+dfsg-1 Severity: grave Justification: renders package unusable Doing a git push on a repository connected to gitlab, I receive this error: BloudFire:repository maqui$ git push origin /usr/share/gitlab-shell/bin/gitlab-shell:10:in `require_relative': cannot load such file -- /usr/share/gitlab-shell/bin/gitlab_init (LoadError) from /usr/share/gitlab-shell/bin/gitlab-shell:10:in `' fatal: No se pudo leer del repositorio remoto. Testing on gitlab server, the file gitlab_init does not exist on this repository. They are a gitlab_init.rb on /usr/lib/ruby/vendor_ruby folder. With this fail, gitlab is unusable, because I cannot commit to the repository or download from it. Thanks, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968), LANGUAGE=en_GB:en (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab-shell depends on: ii libc6 2.27-8 ii ruby 1:2.5.1 gitlab-shell recommends no packages. gitlab-shell suggests no packages. -- debconf-show failed
Bug#914159: gitlab: Problem with GPG Keys
Package: gitlab
Version: 11.1.8+dfsg-2
Severity: normal
After install 11.1.8, importing GPG keys isn't working.
This failure isn't present at 10.8 previous version on Testing.
When I try to upload my GPG key, gitlab gives a 500 internal server error.
After reloading, key are added but without reading the complete key (I think,
beucase gitlab only have detected one of the emails on the key).
Error message on production.log are:
Started POST "/profile/gpg_keys" for x.x.x.x at 2018-11-20 01:30:26 +0100
Processing by Profiles::GpgKeysController#create as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]",
"gpg_key"=>"[FILTERED]", "commit"=>"Add key"}
Completed 500 Internal Server Error in 82ms (ActiveRecord: 1.6ms)
GPGME::Error (Unsupported protocol):
lib/gitlab/gpg.rb:15:in `fingerprints_from_key'
lib/gitlab/gpg.rb:25:in `block in fingerprints_from_key'
lib/gitlab/gpg.rb:93:in `optimistic_using_tmp_keychain'
lib/gitlab/gpg.rb:75:in `block in using_tmp_keychain'
lib/gitlab/gpg.rb:74:in `synchronize'
lib/gitlab/gpg.rb:74:in `using_tmp_keychain'
lib/gitlab/gpg.rb:24:in `fingerprints_from_key'
app/models/gpg_key.rb:111:in `extract_fingerprint'
app/services/gpg_keys/create_service.rb:4:in `execute'
app/controllers/profiles/gpg_keys_controller.rb:10:in `create'
lib/gitlab/i18n.rb:51:in `with_locale'
lib/gitlab/i18n.rb:57:in `with_user_locale'
app/controllers/application_controller.rb:362:in `set_locale'
lib/gitlab/middleware/multipart.rb:97:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:17:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/read_only/controller.rb:38:in `call'
lib/gitlab/middleware/read_only.rb:16:in `call'
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
lib/gitlab/middleware/release_env.rb:10:in `call'
Started GET "/favicon.ico" for x.x.x.x at 2018-11-20 01:30:26 +0100
Started POST "/profile/gpg_keys" for x.x.x.x at 2018-11-20 01:30:32 +0100
Processing by Profiles::GpgKeysController#create as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]",
"gpg_key"=>"[FILTERED]", "commit"=>"Add key"}
[ActiveJob] Enqueued ActionMailer::DeliveryJob (Job ID:
10f8706f-4e6c-4218-ac69-db767782315a) to Sidekiq(mailers) with arguments:
"Notify", "new_gpg_key_email", "deliver_now", 5
Redirected to https://git.example.com/profile/gpg_keys
Completed 302 Found in 1687ms (ActiveRecord: 184.4ms)
On 10.8 version, if I add my GPG key to my profile, I can see all my emails.
Now, on 11.1, I only see one email. I've tested it with the same key always,
but now I didn't have a 10.8 debian installation for re-testing and getting
information from the logfile.
After searching for this bug on gitlab-ce official repository, I can only find
cases with 9.5 version, when gitlab didn't support subkeys. Maybe that's a
problem with the packaging.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitlab depends on:
ii asciidoctor1.5.7.1-1
ii bc 1.07.1-2+b1
ii bundler1.16.1-3
ii bzip2 1.0.6-9
ii dbconfig-pgsql 2.0.10
ii debconf [debconf-2.0] 1.5.69
ii exim4-daemon-light [mail-transport-agent] 4.91-8+b1
ii gitlab-common 11.1.8+dfsg-2
ii gitlab-shell 7.2.0+dfsg-1
ii gitlab-workhorse 5.2.0+debian-2
ii lsb-base 9.20170808
ii nginx 1.14.1-1
ii nginx-full [nginx] 1.14.1-1
ii nodejs 8.11.2~dfsg-1
ii npm5.8.0+ds6-2
ii openssh-client 1:7.9p1-4
ii postgresql-client 11+194
ii postgresql-client-10 [postgresql-client] 10.5-1
ii postgresql-client-11 [postgresql-client] 11.1-1+b1
ii postgresql-contrib 11+194
ii rake 12.3.1-3
ii redis-server 5:5.0.1-1
ii ruby 1:2.5.1
ii ruby-ace-rails-ap 4.1.1-1
ii ruby-acts-as-taggable-on 5.0.0-2
ii ruby-addressable 2.5.2-1
ii ruby-akismet 2.0.0-1
ii ruby-arel
Bug#913581: gitlab: Gitlab API not working
Package: gitlab
Version: 10.8.7+dfsg-1
Severity: important
On a new gitlab installation (10.8.7) API is not working.
I've tested with a migrated installation and a new one (doing purge before
reinstall).
On gitlab check:
Running /usr/share/gitlab-shell/bin/check
Check GitLab API access: FAILED. code: 401
gitlab-shell self-check failed
Try fixing it:
Make sure GitLab is running;
Check the gitlab-shell configuration file:
sudo -u gitlab -H editor /usr/share/gitlab-shell/config.yml
Please fix the error above and rerun the checks.
Trying to reload gitaly (service gitaly restart) do a ok, so service is
apparently working.
Restarting gitaly you can find this on syslog:
Nov 12 17:39:05 systemd[1]: Stopped Gitaly.
Nov 12 17:39:05 systemd[1]: Started Gitaly.
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="Starting Gitaly" version="Gitaly, version 0.100.1+debian2, built "
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00"
level=warning msg="git path not configured. Using default path resolution"
resolvedPath=/usr/bin/git
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00"
level=warning msg="git path not configured. Using default path resolution"
resolvedPath=/usr/bin/git
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="finished tempdir cleaner walk" storage=default time_ms=0
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="listening on unix socket" address=/run/gitlab/sockets/private/gitaly.socket
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="starting RSS monitor" supervisor.name=gitaly-ruby.0
supervisor.rss_threshold=314572800
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="dialing to target with scheme: \"\"" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="ccResolverWrapper: sending new addresses to cc:
[{/tmp/gitaly-ruby307886635/socket.0 0 }]" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="ClientConn switching balancer to \"pick_first\"" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="pickfirstBalancer: HandleSubConnStateChange: 0xc4203742c0, CONNECTING"
system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00"
level=warning msg=spawned supervisor.args="[bundle exec bin/ruby-cd /
/usr/share/gitaly/ruby/bin/gitaly-ruby 13637
/tmp/gitaly-ruby307886635/socket.0]" supervisor.name=gitaly-ruby.0
supervisor.pid=13675
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="grpc: addrConn.createTransport failed to connect to
{/tmp/gitaly-ruby307886635/socket.0 0 }. Err :connection error: desc =
\"transport: Error while dialing dial unix /tmp/gitaly-ruby30$
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="pickfirstBalancer: HandleSubConnStateChange: 0xc4203742c0,
TRANSIENT_FAILURE" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="Failed to dial /tmp/gitaly-ruby307886635/socket.0: context canceled;
please retry." system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="starting RSS monitor" supervisor.name=gitaly-ruby.1
supervisor.rss_threshold=314572800
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="dialing to target with scheme: \"\"" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="ccResolverWrapper: sending new addresses to cc:
[{/tmp/gitaly-ruby307886635/socket.1 0 }]" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="ClientConn switching balancer to \"pick_first\"" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="pickfirstBalancer: HandleSubConnStateChange: 0xc42030c2b0, CONNECTING"
system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="grpc: addrConn.createTransport failed to connect to
{/tmp/gitaly-ruby307886635/socket.1 0 }. Err :connection error: desc =
\"transport: Error while dialing dial unix /tmp/gitaly-ruby30$
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="pickfirstBalancer: HandleSubConnStateChange: 0xc42030c2b0,
TRANSIENT_FAILURE" system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00" level=info
msg="Failed to dial /tmp/gitaly-ruby307886635/socket.1: context canceled;
please retry." system=system
Nov 12 17:39:05 gitaly[13637]: time="2018-11-12T17:39:05+01:00"
level=warning msg=spawned supervisor.args="[bundle exec bin/ruby-cd /
/usr/share/gitaly/ruby/bin/gitaly-ruby 13637
Bug#898228: ruby-gitaly: Required dependency not specified on deb package
Package: ruby-gitaly Version: 0.99.0+dfsg-1 Severity: grave Justification: renders package unusable Gitaly gem requires grpc gem in version 1.10 to work, but, deb package doesn't force installation of this package. In that case, ruby-gitaly is unusable. Error message: Bundler could not find compatible versions for gem "grpc": In Gemfile: grpc (~> 1.3) gitaly-proto (~> 0.88) was resolved to 0.99.0, which depends on grpc (~> 1.10) Could not find gem 'grpc (~> 1.10)', which is required by gem 'gitaly-proto (~> 0.88)', in any of the sources. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-gitaly depends on: ii ruby 1:2.5.1 ii ruby-google-protobuf 3.2.0-2+b2 ii ruby-grpc 1.3.2+debian-4+b1 ruby-gitaly recommends no packages. ruby-gitaly suggests no packages. -- no debconf information
Bug#897444: Gitlab: Change repository path does not work
Package: gitlab Version: 10.6.5+dfsg-1 Severity: normal Changing gitlab repository path does not work. Checking installation give this: GitLab Shell version >= 6.0.4 ? ... OK (6.0.4) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by gitlab:root, or gitlab:gitlab? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty x / x ... repository is empty Configuration changes: /etc/gitlab/gitlab.yml # # 4. Advanced settings # == ## Repositories settings repositories: storages: # You must have at least a `default` storage path. default: path: /home/repositories/ #path: /var/lib/gitlab/repositories/ /etc/gitlab-shell/config.yml # Repositories path # Give the canonicalized absolute pathname, # REPOS_PATH MUST NOT CONTAIN ANY SYMLINK!!! # Check twice that none of the components is a symlink, including "/home". #repos_path: "/var/lib/gitlab/repositories" repos_path: "/home/repositories" /etc/gitaly/config.toml [[storage]] name = "default" #path = "/var/lib/gitlab/repositories" path = "/home/repositories" Gitlab starts correctly. On Admin Area -> Overview -> Projects I can see all repositories with their size computed. On Gitlab interface, entering any project I see message "No repository". At database level, "repository_storage" column contains "default", not any absolute path. Entering on /home/repositories and going to some correct namespace (group / project) I can do a git log and see information. Path are not a symlink. /home is a complete mount point and repositories is a folder inside it. Permission are correct (drwxrws--- 11 gitlab gitlab 4096 Nov 4 20:01 repositories). Where's the problem? Maybe I failed changing some configuration? I'm missing some file for detect it correctly? Thanks for your help. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab depends on: ii adduser3.117 ii asciidoctor1.5.6.2-2 ii bc 1.07.1-2 ii bundler1.16.1-1 ii dbconfig-pgsql 2.0.9 ii debconf [debconf-2.0] 1.5.66 ii exim4-daemon-light [mail-transport-agent] 4.91-3 ii git1:2.17.0-1 ii gitlab-shell 6.0.4+dfsg-1 ii gitlab-workhorse 4.0.0+debian-1 ii lsb-base 9.20170808 ii nginx 1.13.12-1 ii nginx-full [nginx] 1.13.12-1 ii nodejs 8.11.1~dfsg-2 ii npm1.4.21+ds-2 ii openssh-client 1:7.7p1-2 ii postgresql-client 10+190 ii postgresql-client-10 [postgresql-client] 10.3-2 ii postgresql-contrib 10+190 ii rake 12.3.1-2 ii redis-server 5:4.0.9-1 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii ruby-acts-as-taggable-on 5.0.0-2 ii ruby-addressable 2.5.2-1 ii ruby-akismet 2.0.0-1 ii ruby-allocations 1.0.3-1+b4 ii ruby-arel 6.0.4-1 ii ruby-asana 0.6.0-1 ii ruby-asciidoctor-plantuml 0.0.8-1 ii ruby-asset-sync
Bug#894668: gitlab: grape-entity gem update on unstable brokes gitlab
Package: gitlab Version: 10.6.0+dfsg-1 Severity: normal Hi, After update of ruby-grape-entity package, gitlab cannot complete check / installation tasks. Preparing to unpack .../05-ruby-grape-entity_0.7.1-1_all.deb ... Unpacking ruby-grape-entity (0.7.1-1) over (0.6.0-1) ... Setting up gitlab (10.6.0+dfsg-1) ... Creating/updating gitlab user account... Making gitlab owner of /var/lib/gitlab... Could not find gem 'grape-entity (~> 0.6.0)' in any of the gem sources listed in your Gemfile. dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 Required gem are installed but on a new version who arrived unstable 3 days ago. rin:/boot# gem list grape *** LOCAL GEMS *** grape (1.0.2) grape-entity (0.7.1) grape-route-helpers (2.1.0) grape_logging (1.7.0) mustermann-grape (1.0.0) rin:/boot# gem which grape-entity /usr/lib/ruby/vendor_ruby/grape-entity.rb Thanks, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii adduser 3.117 ii asciidoctor 1.5.5-1 ii bc1.07.1-2 ii bundler 1.16.1-1 ii dbconfig-pgsql2.0.9 ii debconf [debconf-2.0] 1.5.66 ii git 1:2.17.0-1 ii gitlab-shell 6.0.4-1 ii gitlab-workhorse 4.0.0+debian-1 ii libjs-chartjs 1.0.2-1 ii libjs-clipboard 1.4.2-1 ii libjs-graphael0.5+dfsg-1 ii libjs-jquery-atwho1.5.4+dfsg.1-2 ii libjs-jquery-caret.js 0.3.1+dfsg.1-2 ii libjs-jquery-nicescroll 3.6.6-1 ii libjs-pdf 1.5.188+dfsg-1 ii libjs-xterm 2.7.0+ds1-1 ii lsb-base 9.20170808 ii nginx 1.13.10-1 ii nginx-full [nginx]1.13.10-1 ii node-babel-core 6.26.0+dfsg-3 ii node-babel-eslint 7.2.3-2 ii node-babel-loader 7.1.2-4 ii node-babel-plugin-transform-define1.3.0-2 ii node-babel-preset-latest 6.26.0+dfsg-3 ii node-babel-preset-stage-2 6.26.0+dfsg-3 ii node-bootstrap-sass 3.3.7-1 ii node-core-js 2.4.1-2 ii node-d3-array 1.2.1-3 ii node-d3-axis 1.0.8-3 ii node-d3-brush 1.0.4-3 ii node-d3-scale 1.0.6-3 ii node-d3-selection 1.1.0-3 ii node-d3-shape 1.2.0-2 ii node-d3-time 1.0.7-2 ii node-d3-time-format 2.0.5-2 ii node-debug3.1.0-1 ii node-exports-loader 0.6.4-1 ii node-file-loader 0.11.2-1 ii node-glob 7.1.2-5 ii node-imports-loader 0.7.1-1 ii node-jed 1.1.1-1 ii node-jquery 2.2.4+dfsg-2 ii node-js-cookie2.2.0-1 ii node-jszip3.1.4+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-1 ii node-katex0.8.3+dfsg-1 ii node-lie 3.1.1+dfsg-1 ii node-marked 0.3.9+dfsg-1 ii node-mousetrap1.6.1+ds-1 ii node-raw-loader 0.5.1-1 ii node-stats-webpack-plugin 0.6.1-1 ii node-underscore 1.8.3~dfsg-1 ii node-url-loader 0.5.9-1 ii nodejs8.9.3~dfsg-12 ii npm 1.4.21+ds-2 ii openssh-client1:7.6p1-5 ii postfix [mail-transport-agent]3.3.0-1 ii postgresql-client 10+190 ii postgresql-client-10 [postgresql-client] 10.3-2 ii postgresql-contrib10+190 ii rake 12.3.1-1 ii redis-server 5:4.0.9-1 ii ruby 1:2.5.1 ii
Bug#894272: gitlab: Problem on upgrade from 8.13 - 9.5 - 10.5. Probably local setup problem
Package: gitlab
Version: 10.5.6+dfsg-1
Severity: normal
Hi,
I have a gitlab installation working originally on 8.13 version.
This installation stop working when some upgrades for 9.5 enters testing.
I have the same failure from my test installation, some gems installed locally.
History are:
I've upgrade 8.13 to 9.5.4+dfsg-7. Not working because sprockets problem.
I've upgrade 9.5.4 to 10.5.5+dfsg-3. Not working because sprockets problem.
I've done a full backup of installation and database, deleted all locally
installed gems, apt-get remove gitlab && apt-get remove ruby && purge gitlab &&
apt-get install gitlab.
As I've detected, on some cases, purge fails because there's some process
running as gitlab user.
My problem:
After a full delete of gitlab & ruby and another dependences, I've do a clean
install (without restore any backup yet).
Gitlab installs correctly, but, there's a problem starting sidekiq. There's the
log:
Child worker:
AssetSize Chunks Chunk Names
c3789bfe47e4e75a43bd.worker.js 188 kBmain [emitted] main
[../../../../../../var/lib/gitlab/.node_modules/diff/dist/diff.js]
/var/lib/gitlab/.node_modules/diff/dist/diff.js 184 kB {main} [built]
[../../../../../lib/nodejs/babel-loader/lib/index.js!./ide/lib/diff/diff_worker.js]
/usr/lib/nodejs/babel-loader/lib!./ide/lib/diff/diff_worker.js + 1 modules 1.1
kB {main} [built]
A dependency job for gitlab.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript gitlab, action "start" failed.
● gitlab.service - GitLab Services
Loaded: loaded (/lib/systemd/system/gitlab.service; enabled; vendor preset:
enabled)
Active: inactive (dead) since Thu 2018-03-22 10:43:41 CET; 5 days ago
Main PID: 4989 (code=exited, status=0/SUCCESS)
Mar 27 19:12:51 kanade.darkbolt.net systemd[1]: Dependency failed for GitLab
Services.
Mar 27 19:12:51 kanade.darkbolt.net systemd[1]: gitlab.service: Job
gitlab.service/start failed with result 'dependency'.
Mar 27 19:27:39 kanade.darkbolt.net systemd[1]: Dependency failed for GitLab
Services.
Mar 27 19:27:39 kanade.darkbolt.net systemd[1]: gitlab.service: Job
gitlab.service/start failed with result 'dependency'.
Mar 27 20:24:02 kanade.darkbolt.net systemd[1]: Dependency failed for GitLab
Services.
Mar 27 20:24:02 kanade.darkbolt.net systemd[1]: gitlab.service: Job
gitlab.service/start failed with result 'dependency'.
Mar 28 02:15:30 kanade.darkbolt.net systemd[1]: Dependency failed for GitLab
Services.
Mar 28 02:15:30 kanade.darkbolt.net systemd[1]: gitlab.service: Job
gitlab.service/start failed with result 'dependency'.
Mar 28 02:27:00 kanade.darkbolt.net systemd[1]: Dependency failed for GitLab
Services.
Mar 28 02:27:00 kanade.darkbolt.net systemd[1]: gitlab.service: Job
gitlab.service/start failed with result 'dependency'.
dpkg: error processing package gitlab (--configure):
installed gitlab package post-installation script subprocess returned error
exit status 1
Processing triggers for systemd (238-3) ...
Errors were encountered while processing:
gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)
kanade:~# journalctl -xe
-- Subject: Unit gitlab-mailroom.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gitlab-mailroom.service has finished starting up.
--
-- The start-up result is RESULT.
Mar 28 02:26:28 kanade.darkbolt.net gitlab-workhorse[29141]:
time="2018-03-28T02:26:28+02:00" level=info msg=Starting
version="gitlab-workhorse (unknown version)"
Mar 28 02:26:29 kanade.darkbolt.net gitlab-sidekiq[29135]: bundler: failed to
load command: sidekiq (/usr/local/bin/sidekiq)
Mar 28 02:26:29 kanade.darkbolt.net gitlab-sidekiq[29135]: LoadError: cannot
load such file -- /usr/share/rubygems-integration/all/specifications/bin/sidekiq
Mar 28 02:26:29 kanade.darkbolt.net gitlab-sidekiq[29135]:
/usr/local/bin/sidekiq:23:in `load'
Mar 28 02:26:29 kanade.darkbolt.net gitlab-sidekiq[29135]:
/usr/local/bin/sidekiq:23:in `'
Mar 28 02:26:29 kanade.darkbolt.net systemd[1]: gitlab-sidekiq.service: Main
process exited, code=exited, status=1/FAILURE
Mar 28 02:27:00 kanade.darkbolt.net systemd[1]: gitlab-sidekiq.service: Failed
with result 'exit-code'.
Mar 28 02:27:00 kanade.darkbolt.net systemd[1]: Failed to start GitLab Sidekiq
Worker.
-- Subject: Unit gitlab-sidekiq.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gitlab-sidekiq.service has failed.
--
-- The result is RESULT.
Mar 28 02:27:00 kanade.darkbolt.net systemd[1]: Dependency failed for GitLab
Services.
-- Subject: Unit gitlab.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gitlab.service has failed.
--
-- The result is RESULT.
Mar 28 02:27:00 kanade.darkbolt.net systemd[1]: gitlab.service: Job
gitlab.service/start failed with result 'dependency'.
Mar 28 02:27:00 kanade.darkbolt.net
Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install
Package: gitlab Version: 10.5.6+dfsg-1 Severity: grave Justification: renders package unusable Hi, Installing gitlab 10.5.6 do not work because a problem on sprockets. This error is also on old 10.5.5 and 9.5.4 versions. Thanks, Precompiling assets... /usr/lib/ruby/vendor_ruby/builder/xchar.rb:111: warning: constant ::Fixnum is deprecated rake aborted! Sprockets::Error: manifest requires environment for compilation /var/lib/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/manifest.rb:178:in `compile' /var/lib/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `' Tasks: TOP => assets:precompile (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii adduser 3.117 ii asciidoctor 1.5.5-1 ii bc1.07.1-2 ii bundler 1.16.1-1 ii dbconfig-pgsql2.0.9 ii debconf [debconf-2.0] 1.5.66 ii git 1:2.16.3-1 ii gitlab-shell 6.0.4-1 ii gitlab-workhorse 3.8.0+debian-1 ii libjs-chartjs 1.0.2-1 ii libjs-clipboard 1.4.2-1 ii libjs-graphael0.5+dfsg-1 ii libjs-jquery-atwho1.5.4+dfsg.1-2 ii libjs-jquery-caret.js 0.3.1+dfsg.1-2 ii libjs-jquery-nicescroll 3.6.6-1 ii libjs-pdf 1.5.188+dfsg-1 ii libjs-xterm 2.7.0+ds1-1 ii lsb-base 9.20170808 ii nginx 1.13.10-1 ii nginx-full [nginx]1.13.10-1 ii node-babel-core 6.26.0+dfsg-3 ii node-babel-eslint 7.2.3-2 ii node-babel-loader 7.1.2-4 ii node-babel-plugin-transform-define1.3.0-2 ii node-babel-preset-latest 6.26.0+dfsg-3 ii node-babel-preset-stage-2 6.26.0+dfsg-3 ii node-bootstrap-sass 3.3.7-1 ii node-core-js 2.4.1-2 ii node-d3-array 1.2.1-3 ii node-d3-axis 1.0.8-3 ii node-d3-brush 1.0.4-3 ii node-d3-scale 1.0.6-3 ii node-d3-selection 1.1.0-3 ii node-d3-shape 1.2.0-2 ii node-d3-time 1.0.7-2 ii node-d3-time-format 2.0.5-2 ii node-debug3.1.0-1 ii node-exports-loader 0.6.4-1 ii node-file-loader 0.11.2-1 ii node-glob 7.1.2-5 ii node-imports-loader 0.7.1-1 ii node-jed 1.1.1-1 ii node-jquery 2.2.4+dfsg-2 ii node-js-cookie2.2.0-1 ii node-jszip3.1.4+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-1 ii node-katex0.8.3+dfsg-1 ii node-lie 3.1.1+dfsg-1 ii node-marked 0.3.9+dfsg-1 ii node-mousetrap1.6.1+ds-1 ii node-raw-loader 0.5.1-1 ii node-stats-webpack-plugin 0.6.1-1 ii node-underscore 1.8.3~dfsg-1 ii node-url-loader 0.5.9-1 ii nodejs8.9.3~dfsg-12 ii npm 1.4.21+ds-2 ii openssh-client1:7.6p1-4 ii postfix [mail-transport-agent]3.3.0-1 ii postgresql-client 10+190 ii postgresql-client-10 [postgresql-client] 10.3-2 ii postgresql-contrib10+190 ii rake 12.3.1-1 ii redis-server 5:4.0.8-2 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii ruby-acts-as-taggable-on 5.0.0-2 ii ruby-addressable 2.5.2-1 ii ruby-akismet
Bug#893867: gitlab: Dpkg fail to configure gitlab package. Problem with some Ruby Gems on 10.5
Package: gitlab Version: 10.5.5+dfsg-2 Severity: grave Justification: renders package unusable Gitlab 10.5.5+dfsg-1 and 10.5.5+dfsg-2 fails to install. The machine have a gitlab 9.5.4 installed (since Experimental upload), upgrading to 10.5.5 on unstable. This is the error on installation: Running final rake tasks and tweaks... gitlab_production database is not empty, skipping gitlab setup /usr/lib/ruby/vendor_ruby/builder/xchar.rb:111: warning: constant ::Fixnum is deprecated rake aborted! NameError: uninitialized constant Rouge::Lexers::Plantuml /usr/share/gitlab/config/initializers/plantuml_lexer.rb:2:in `' /usr/share/gitlab/config/environment.rb:5:in `' /var/lib/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `' Tasks: TOP => db:migrate => environment (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 The xchar.rb message appears from 9.5.4 version. Also, if it's relevant, the latest 9.5.4+dfsg-7 does not install too, with another error: Precompiling assets... /usr/lib/ruby/vendor_ruby/builder/xchar.rb:111: warning: constant ::Fixnum is deprecated DEPRECATION WARNING: `jws_private_key` has been replaced by `signing_key` and will be removed in a future version, please remove it from config/initializers/doorkeeper_openid_connect.rb rake aborted! Sprockets::Error: manifest requires environment for compilation /var/lib/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/manifest.rb:178:in `compile' /var/lib/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `' Tasks: TOP => assets:precompile (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 10.5.5 tested only on one machine. 9.5.4 error is tested on two different installations. None of them are clear machines without any old gitlab version installed. Thanks, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii adduser 3.117 ii asciidoctor 1.5.5-1 ii bc1.07.1-2 ii bundler 1.16.1-1 ii dbconfig-pgsql2.0.9 ii debconf [debconf-2.0] 1.5.66 ii git 1:2.16.2-1 ii gitlab-shell 6.0.4-1 ii gitlab-workhorse 3.8.0+debian-1 ii libjs-chartjs 1.0.2-1 ii libjs-clipboard 1.4.2-1 ii libjs-graphael0.5+dfsg-1 ii libjs-jquery-atwho1.5.4+dfsg.1-2 ii libjs-jquery-caret.js 0.3.1+dfsg.1-2 ii libjs-jquery-nicescroll 3.6.6-1 ii libjs-pdf 1.5.188+dfsg-1 ii libjs-xterm 2.7.0+ds1-1 ii lsb-base 9.20170808 ii nginx 1.13.10-1 ii nginx-full [nginx]1.13.10-1 ii node-babel-core 6.26.0+dfsg-3 ii node-babel-eslint 7.2.3-2 ii node-babel-loader 7.1.2-4 ii node-babel-plugin-transform-define1.3.0-2 ii node-babel-preset-latest 6.26.0+dfsg-3 ii node-babel-preset-stage-2 6.26.0+dfsg-3 ii node-bootstrap-sass 3.3.7-1 ii node-core-js 2.4.1-2 ii node-d3-array 1.2.1-3 ii node-d3-axis 1.0.8-3 ii node-d3-brush 1.0.4-3 ii node-d3-scale 1.0.6-3 ii node-d3-selection 1.1.0-3 ii node-d3-shape 1.2.0-2 ii node-d3-time 1.0.7-2 ii node-d3-time-format 2.0.5-2 ii node-debug3.1.0-1 ii node-exports-loader 0.6.4-1 ii node-file-loader 0.11.2-1 ii node-glob 7.1.2-5 ii node-imports-loader 0.7.1-1 ii node-jed 1.1.1-1 ii node-jquery 2.2.4+dfsg-2 ii node-js-cookie2.2.0-1 ii node-jszip3.1.4+dfsg-1 ii
Bug#840464: nodejs: 'npm install' command fails with compilation error in Kerberos header
Package: nodejs Version: 0.10.29~dfsg-2 Severity: normal Dear Maintainer, After installing packages "nodejs", "nodejs-legacy", and "libkrb5-dev", I still get a compilation error blocking completion of "npm install mongodb"... > kerberos@0.0.21 install > /home/dllamber/src/project2/node_modules/mongodb/node_modules/kerberos > (node-gyp rebuild) || (exit 0) make: Entering directory '/home/dllamber/src/project2/node_modules/mongodb/node_modules/kerberos/build' CXX(target) Release/obj.target/kerberos/lib/kerberos.o In file included from ../lib/kerberos.h:9:0, from ../lib/kerberos.cc:1: ../node_modules/nan/nan.h:324:47: error: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’ static const unsigned kReplaceInvalidUtf8 = v8::String::REPLACE_INVALID_UTF8; ^ kerberos.target.mk:88: recipe for target 'Release/obj.target/kerberos/lib/kerberos.o' failed make: *** [Release/obj.target/kerberos/lib/kerberos.o] Error 1 make: Leaving directory '/home/dllamber/src/project2/node_modules/mongodb/node_modules/kerberos/build' gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/share/node-gyp/lib/build.js:267:23) gyp ERR! stack at ChildProcess.emit (events.js:98:17) gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:809:12) gyp ERR! System Linux 3.16.0-4-686-pae gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild" gyp ERR! cwd /home/dllamber/src/project2/node_modules/mongodb/node_modules/kerberos gyp ERR! node -v v0.10.29 gyp ERR! node-gyp -v v0.12.2 gyp ERR! not ok mongodb@2.0.55 node_modules/mongodb ├── es6-promise@2.1.1 ├── readable-stream@1.0.31 (inherits@2.0.3, isarray@0.0.1, string_decoder@0.10.31, core-util-is@1.0.2) ├── kerberos@0.0.21 (nan@2.3.5) └── mongodb-core@1.2.31 (bson@0.4.23) As per user "kathiedrt"'s comment on https://github.com/nodejs/nan/issues/414 ,: "I just did a "npm -g install npm" to upgrade the debian's npm to npm's npm and that presumably included node-gyp and that fixed it so thanks..." However, that doesn't sound like the Debian way of doing things ... ? -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nodejs depends on: ii libc-ares21.10.0-2 ii libc6 2.19-18+deb8u4 ii libgcc1 1:4.9.2-10 ii libssl1.0.0 1.0.1t-1+deb8u2 ii libstdc++64.9.2-10 ii libv8-3.14.5 3.14.5.8-8.1 ii zlib1g1:1.2.8.dfsg-2+b1 nodejs recommends no packages. nodejs suggests no packages. -- no debconf information
Bug#827789: Upgrade mostly fixed this bug
After my last upgrade, about a week or so ago, this bug has mostly disappeared. My machine reliably wakes up from suspension with both monitors working, and not mirrored. The only odd thing is that, although I start out with different desktop images (photographs) on the two monitors, once I wake the computer up from suspend, the second screen has the same desktop image as the first one. This is not a problem, of course, but I thought I should report it. I'm sorry that I don't have the exact date when I upgraded and found the problem fixed, but I had become accustomed to shutting the computer off rather than suspending it, and had disabled suspending after a period of inactivity. I now have re-enabled both and it works great. A further upgrade (to the current testing (stretch)) last night (8/9/16) seems to continue to work correctly, although the desktop image on screen #2 is still changing to the image from screen #1 after waking the machine up. Neither of these upgrades replaced any xfce4 packages, or any xorg packages (I don't think it did, anyway). The kernel was upgraded to, I believe, linux-image-4.6.0-1-amd64_4.6.4-1_amd64.deb (I'm not on that computer right now, but this one was upgraded at the same time, and has the same architecture --- but only one monitor). -- David L. Johnson Department of Mathematics Lehigh University
Bug#829268: lyx: toolbar icons do not show up with upgrade to lyx-2.2.0; needed qt-svc not installed
Package: lyx Version: 2.2.0-1 Severity: important Dear Maintainer, I just upgraded my system (debian testing), and an upgrade of lyx to 2.2.0 was part of the upgrade. I am a constant lyx user, so this is vital to my work. When I ran the new version, the toolbar icons did not show up, instead showing text descriptions --- they didn't fit on the space available, and were a mess. The terminal window where I had started lyx had all sorts of error messages about not being able to load icons. I googled to find a similar problem someone had (on ubuntu), and saw that it required qt-svg packages. I installed the packages libqt5svg5 qtsvg5-dbg libqtscript4-svg --- I am not sure they were all needed, particularly the middle one), and then the icons displayed correctly. It looks like the package dependencies aren't quite right for this version of lyx. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lyx depends on: ii libboost-signals1.58.0 1.58.0+dfsg-5.1 ii libc6 2.22-11 ii libenchant1c2a 1.6.0-11+b1 ii libgcc1 1:6.1.1-7 ii libmagic1 1:5.25-2 ii libmythes-1.2-0 2:1.2.4-1 ii libqtcore4 4:4.8.7+dfsg-8 ii libqtgui4 4:4.8.7+dfsg-8 ii libstdc++6 6.1.1-7 ii lyx-common 2.2.0-1 ii xdg-utils 1.1.1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages lyx recommends: ii dvipng 1.14-2+b2 ii evince [pdf-viewer] 3.20.1-1 ii fonts-lyx2.2.0-1 ii ghostscript 9.19~dfsg-1+b1 ii gv [pdf-viewer] 1:3.7.4-1 ii imagemagick 8:6.8.9.9-7.1 ii poppler-utils0.44.0-3 ii preview-latex-style 11.87-3+deb8u1 ii psutils 1.17.dfsg-2 ii tex4ht 20090611-3 ii texlive-fonts-recommended2016.20160623-1 ii texlive-generic-extra2016.20160623-1 ii texlive-generic-recommended 2016.20160623-1 ii texlive-latex-extra 2016.20160623-1 ii texlive-latex-recommended2016.20160623-1 ii texlive-science 2016.20160623-1 Versions of packages lyx suggests: ii chktex1.7.4-1+b1 pn etoolbox pn gnuhtml2latex pn groff pn latex2rtf pn librsvg2-bin | inkscape pn libtiff-tools pn linuxdoc-tools pn lyx-dbg pn noweb pn rcs pn sgmltools-lite ii texlive-latex-recommended [latex-xcolor] 2016.20160623-1 ii texlive-xetex 2016.20160623-1 pn writer2latex pn wv -- no debconf information
Bug#827789: xfce4-settings: Upon reviving system from suspend, second monitor always is a mirror of first.
Package: xfce4-settings Version: 4.12.0-3 Severity: normal Dear Maintainer, I had reported that my second monitor would not wake up after suspend with 4.5 or newer kernels. That was fixed with xfce-settings-4.12.0-3 (appeared on testing this week), but now when I wake the system up from sleep the second monitor is mirrored from the first, even though I did not set it that way in the settings window. Try as I may, the settings go away after suspend. It works correctly at initial boot, but once it goes to sleep it wakes up mirrored. It can be re-set each time, but that is a nuisance. My system is a Gigabyte brix i3, GB-BXi3-4010. Monitor #1 is connected via the one HDMI port, second monitor connected via a mini-dp port. It worked fine with kernel 4.3 and xfce4-4.12.0-1. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-settings depends on: ii libc62.22-11 ii libcairo21.14.6-1+b1 ii libdbus-1-3 1.10.8-1 ii libdbus-glib-1-2 0.106-1 ii libexo-1-0 0.10.7-1 ii libfontconfig1 2.11.0-6.4 ii libgarcon-1-00.4.0-2 ii libgarcon-common 0.4.0-2 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.48.1-1 ii libgtk2.0-0 2.24.30-2 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libupower-glib3 0.99.4-3 ii libx11-6 2:1.6.3-1 ii libxcursor1 1:1.1.14-1+b1 ii libxfce4ui-1-0 4.12.1-2 ii libxfce4util74.12.1-2 ii libxfconf-0-24.12.0-2+b1 ii libxi6 2:1.7.6-1 ii libxklavier165.2.1-1 ii libxrandr2 2:1.5.0-1 ii xfconf 4.12.0-2+b1 Versions of packages xfce4-settings recommends: ii x11-utils 7.7+3 xfce4-settings suggests no packages. -- no debconf information
Bug#826187: [Pkg-xfce-devel] Bug#826187: Fwd: xfce4 second monitor does not wake up after suspend, with kernel 4.5.0-1 or 4.5.0-2
On Sat, 04 Jun 2016 10:27:57 +0200 Yves-Alexis Perez <cor...@debian.org> wrote: > On ven., 2016-06-03 at 00:46 -0400, David L. Johnson wrote: > > Sorry to report this outside of reportbug, but I clearly did not get it > > configured correctly with my e-mail server (which is tls-protected) and, > > frankly, I don't want to go through the installation again after losing > > my entire bug report when it could not connect to the e-mail server. > > Except that it gives use valuable information on your system. So please fix > your setup and use reportbug again so we have an idea how to help you. What > would be especially helpful here is your architecture, if we want to provide > you a test package⦠> > Regards, > -- > Yves-Alexis > > Yves-Alexis: I have tried 4 times to re-send this through reportbug. It hangs at sending the bug, and the "No" choice when it asks to re-try does not, as it claimed, save the report. Sorry, but that is a pain in the ass. Ask me anything about my system, but please don't ask me to re-configure reportbug again. The options available just do not work. Yes, I know my smtp server, and know how to connect to it, but whatever reportbug is doing it doesn't work. Even the following does not work: # If nothing else works, remove the # at the beginning # of the following three lines: no-cc header "X-Debbugs-CC: david.john...@lehigh.edu" smtphost reportbug.debian.org -- David L. Johnson Department of Mathematics Lehigh University
Bug#826187: [Pkg-xfce-devel] Bug#826187: Fwd: xfce4 second monitor does not wake up after suspend, with kernel 4.5.0-1 or 4.5.0-2
> Except that it gives use valuable information on your system. So please fix > your setup and use reportbug again so we have an idea how to help you. What > would be especially helpful here is your architecture, if we want to provide > you a test package I did mention that, although I know the bug report was too long. "(gigabite brix i3, GB-BXi3-4010) with debian testing (amd64) and xfce4 4.12" I just upgraded to kernel 4.6.0-1-amd64, but the behavior persists, although with my old 4.3.0-1 kernel both screens wake up like they are supposed to. -- David L. Johnson Department of Mathematics Lehigh University
Bug#826187: Fwd: xfce4 second monitor does not wake up after suspend, with kernel 4.5.0-1 or 4.5.0-2
Package: xfce4 Version: 4.12.3 BTW: I tried to report this with reportbug, but it could not connect with my e-mail server and I lost all of that data. I am trying again. The situation is this. I have a dual-monitor system (gigabite brix i3, GB-BXi3-4010) with debian testing (amd64) and xfce4 4.12. Upon initial installation, the second monitor worked perfectly, somewhat to my surprise. This new machine has been the easiest by far of all machines I have installed debian on. However, with an upgrade that moved the kernel from 4.3.0-1 to 4.5.0-1 and now 4.5.0-2 (current as of 5/31/16), the second monitor does not wake up after a suspend or when xscreensaver kicks in. The second monitor is connected via a mini-dp port, the primary monitor is hdmi. I only have one hdmi port. Booting with the old 4.3.-1 kernel solves the problem, but the 4.5 kernels do seem to be faster, and I want to stay current with debian testing. Setting the option "configure new screens when connected" in the xfce4 screen dialog box gives me a window in the one functioning monitor that allows me to choose two monitors, and, after several clicks on that choice (4 or 5), will start the second monitor and return everything to normal. But this should be fixed. I reported this bug to the xfce4 website, and was told to try a patch, but that would require building the gui package from source, and would be outside of the debian packaging system, which in my experience creates more problems than it solves. I am hoping for a patched xfce4 package. The relevant thread is https://bugzilla.xfce.org/show_bug.cgi?id=11627, which referred me back to their bug #11107. I did not try that patch, since it would involve re-building of the whole xfce4 suite, which would most likely break something else and which would no longer be in sync with my otherwise completely debian system. xfce4 version is current, 4.12, system is current debian testing (last updated 5/31/16), with kernel 4.5.0-2, but this occurred with 4.5.0-1 as well, and was reported to xfce folks as also being a problem with kernel 4.4.* as the bug report I mentioned states. Currently the work-around I have found using the nonstandard xfce4 setting to find new monitors will work, but without it the system seems to not even recognize the second monitor. Asking it to look for the second monitor several times will also work; this "configure new displays" option just makes that a little easier. Let me be clear about one thing: I do not want to go to the gnome gui system. Previous machines used that, and when it switched to the newer version (gnome-3 I believe) it was so horrible I went out of my way to eliminate all gnome programs. This machine is gnome-free, and I want to keep it that way. Sorry to report this outside of reportbug, but I clearly did not get it configured correctly with my e-mail server (which is tls-protected) and, frankly, I don't want to go through the installation again after losing my entire bug report when it could not connect to the e-mail server. Here is the output of dpkg --status xfce4: Package: xfce4 Status: install ok installed Priority: optional Section: xfce Installed-Size: 16 Maintainer: Debian Xfce Maintainers <pkg-xfce-de...@lists.alioth.debian.org> Architecture: all Version: 4.12.3 Depends: xfwm4 (>= 4.12.0), xfconf (>= 4.12.0), xfce4-settings (>= 4.12.0), xfce4-panel (>= 4.12.0), xfdesktop4 (>= 4.12.0), thunar (>= 1.6.6), gtk2-engines-xfce (>= 3.2.0), xfce4-session (>= 4.12.0), xfce4-appfinder (>= 4.12.0), xfce4-pulseaudio-plugin, orage (>= 4.12.0), libxfce4ui-utils (>= 4.12) Recommends: xorg, desktop-base (>= 5.0.4), thunar-volman (>= 0.8.1), tango-icon-theme (>= 0.8.90), xfce4-notifyd Suggests: xfce4-goodies, xfce4-power-manager (>= 1.4.0), gtk3-engines-xfce (>= 3.2.0) Description: Meta-package for the Xfce Lightweight Desktop Environment Xfce is a lightweight desktop environment for unix-like operating systems. It aims to be fast and lightweight, while still being visually appealing and easy to use. Designed for productivity, it loads and executes applications fast, while conserving system resources. . This package is a metapackage; it depends on the core packages of the Xfce4 desktop environment and recommends some extra Xfce4 packages. If you intend to use Xfce4 and want the full experience then installing this package and the packages it Recommends is a great place to start. If you just want to pick and choose the core components then feel free to remove this package. -- David L. Johnson Department of Mathematics Lehigh University
Bug#805196: Also doesn't work with "testing"
Installed version 1.0.25-2 from "testing", rebooted, same behavior. Process is in an unkillable hang, and the last line of "lsof -c scanimage" is scanimage 3477 davidl 71r CHR 99,0 0t08854 /dev/parport0 FWIW, this is on an IBM ThinkCentre, has a parallel port, nothing is plugged into it. -- David Lee Lambert * KD8WQF * (cell) +1 586-873-8813 IM: davidleelambert (Yahoo!, Skype and Google Talk) "Justicia, Tierra y Libertad"
Bug#805196: sane: xsane, scanimage -L, etc. hang
Yes, it's still present in "experimental". Will check "unstable" as well. Interestingly, the "scanimage -L" process is unkillable, not by "Ctrl+C", nor by "kill -9", and here's the end of "lsof" over it... scanimage 23808 root 66r FIFO0,8 0t0 2197502 pipe scanimage 23808 root 67w FIFO0,8 0t0 2197502 pipe scanimage 23808 root 68r FIFO0,8 0t0 2197503 pipe scanimage 23808 root 69w FIFO0,8 0t0 2197503 pipe scanimage 23808 root 70u 0,906902 anon_inode scanimage 23808 root 71r REG 254,0 2125 475696 /etc/sane.d/mustek.conf scanimage 23808 root 72r CHR 99,0 0t09359 /dev/parport0 On 01/17/2016 03:33 PM, Jörg Frings-Fürst wrote: tags 805196 + moreinfo thanks Hello David, please can you test if your bug exists with the sane-backends from unstable/testing 1.0.25-2 and from experimental 1.0.26~git20151121-1? Many thanks CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54538 Bausendorf Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. -- David Lee Lambert * KD8WQF * (cell) +1 586-873-8813 IM: davidleelambert (Yahoo!, Skype and Google Talk) "Justicia, Tierra y Libertad"
Bug#768480: lincity-ng: Start Up Causes Black Screen After Booting Latest Kernel
Package: lincity-ng Version: 2.0-4+b1 Severity: important Dear Maintainer, After applying normal morning Sid update, launching lincity-ng in XFCE environment brings up black screen with centered X-pointer and non-functional mouse buttons. After about half a minute, nouveau complains in kern.log: E[lincity-ng[2108]] failed to idle channel 0x [lincity-ng[2108]] Killing lincity with HUP locks up the system for about half a minute. What aptitude did: Start-Date: 2014-11-07 11:36:44 Reinstall: man-db:amd64 (2.7.0.2-3) Upgrade: multiarch-support:amd64 (2.19-12, 2.19-13), linux-doc-3.16:amd64 (3.16.7-1, 3.16.7-2), linux-image-3.16.0-4-amd64:amd64 (3.16.7-1, 3.16.7-2), libpaper1:amd64 (1.1.24+nmu3, 1.1.24+nmu4), libc6-dev-x32:amd64 (2.19-12, 2.19-13), libgssapi-krb5-2:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), hyphen-en-us:amd64 (2.8.8-1, 2.8.8-2), libc6-dev-i386:amd64 (2.19-12, 2.19-13), libkrb5-3:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), libpcsclite1:amd64 (1.8.12-1, 1.8.13-1), libcogl-common:amd64 (1.18.2-2, 1.18.2-3), libnetpbm10:amd64 (10.0-15.1+b1, 10.0-15.2), libc-dev-bin:amd64 (2.19-12, 2.19-13), libapparmor1:amd64 (2.9.0-1, 2.9.0-2), libc-bin:amd64 (2.19-12, 2.19-13), libc6:amd64 (2.19-12, 2.19-13), gstreamer0.10-tools:amd64 (0.10.36-1.4, 0.10.36-1.5), openjdk-7-jdk:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), curl:amd64 (7.38.0-2, 7.38.0-3), libbrlapi0.6:amd64 (5.2~20141018-1, 5.2~20141018-2), linux-headers-3.16.0-4-amd64:amd64 (3.16.7-1, 3.16.7-2), libsqlite3-0:amd64 (3.8.7-1, 3.8.7.1-1), openjdk-7-j re-headless:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), libhyphen0:amd64 (2.8.8-1, 2.8.8-2), glibc-doc:amd64 (2.19-12, 2.19-13), krb5-locales:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), wget:amd64 (1.16-2, 1.16-3), linux-support-3.16.0-4:amd64 (3.16.7-1, 3.16.7-2), netpbm:amd64 (10.0-15.1+b1, 10.0-15.2), openjdk-7-jre:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), linux-compiler-gcc-4.8-x86:amd64 (3.16.7-1, 3.16.7-2), libcurl3:amd64 (7.38.0-2, 7.38.0-3), libc6-i386:amd64 (2.19-12, 2.19-13), icedtea-7-jre-jamvm:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), openjdk-7-demo:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), libpaper-utils:amd64 (1.1.24+nmu3, 1.1.24+nmu4), libc6-dbg:amd64 (2.19-12, 2.19-13), linux-libc-dev:amd64 (3.16.7-1, 3.16.7-2), linux-headers-3.16.0-4-common:amd64 (3.16.7-1, 3.16.7-2), libgstreamer0.10-0:amd64 (0.10.36-1.4, 0.10.36-1.5), locales:amd64 (2.19-12, 2.19-13), locales-all:amd64 (2.19-12, 2.19-13), libkrb5support0:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), libk5crypto3:amd64 (1.12.1+dfsg-11, 1. 12.1+dfsg-13), libc6-dev:amd64 (2.19-12, 2.19-13), libcurl3-gnutls:amd64 (7.38.0-2, 7.38.0-3), libc6-x32:amd64 (2.19-12, 2.19-13) End-Date: 2014-11-07 11:39:36 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lincity-ng depends on: ii libc6 2.19-13 ii libgcc1 1:4.9.2-1 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libphysfs12.0.3-2 ii libsdl-gfx1.2-5 2.0.25-4 ii libsdl-image1.2 1.2.12-5+b4 ii libsdl-mixer1.2 1.2.12-11+b1 ii libsdl-ttf2.0-0 2.0.11-3 ii libsdl1.2debian 1.2.15-10 ii libstdc++64.9.2-1 ii libxml2 2.9.2+dfsg1-1 ii lincity-ng-data 2.0-4 ii ttf-dejavu2.34-1 ii zlib1g1:1.2.8.dfsg-2 lincity-ng recommends no packages. lincity-ng suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768480: Edited Aptitude Log
Readable and sorted aptitude history: Start-Date: 2014-11-07 11:36:44 Reinstall: man-db:amd64(2.7.0.2-3) Upgrade: curl:amd64 (7.38.0-2, 7.38.0-3), glibc-doc:amd64 (2.19-12, 2.19-13), gstreamer0.10-tools:amd64 (0.10.36-1.4, 0.10.36-1.5), hyphen-en-us:amd64 (2.8.8-1, 2.8.8-2), icedtea-7-jre-jamvm:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), krb5-locales:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), libapparmor1:amd64 (2.9.0-1, 2.9.0-2), libbrlapi0.6:amd64 (5.2~20141018-1, 5.2~20141018-2), libc-bin:amd64 (2.19-12, 2.19-13), libc-dev-bin:amd64 (2.19-12, 2.19-13), libc6-dbg:amd64 (2.19-12, 2.19-13), libc6-dev-i386:amd64(2.19-12, 2.19-13), libc6-dev-x32:amd64 (2.19-12, 2.19-13), libc6-dev:amd64 (2.19-12, 2.19-13), libc6-i386:amd64(2.19-12, 2.19-13), libc6-x32:amd64 (2.19-12, 2.19-13), libc6:amd64 (2.19-12, 2.19-13), libcogl-common:amd64(1.18.2-2, 1.18.2-3), libcurl3-gnutls:amd64 (7.38.0-2, 7.38.0-3), libcurl3:amd64 (7.38.0-2, 7.38.0-3), libgssapi-krb5-2:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), libgstreamer0.10-0:amd64(0.10.36-1.4, 0.10.36-1.5), libhyphen0:amd64(2.8.8-1, 2.8.8-2), libk5crypto3:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), libkrb5-3:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), libkrb5support0:amd64 (1.12.1+dfsg-11, 1.12.1+dfsg-13), libnetpbm10:amd64 (10.0-15.1+b1, 10.0-15.2), libpaper-utils:amd64(1.1.24+nmu3, 1.1.24+nmu4), libpaper1:amd64 (1.1.24+nmu3, 1.1.24+nmu4), libpcsclite1:amd64 (1.8.12-1, 1.8.13-1), libsqlite3-0:amd64 (3.8.7-1, 3.8.7.1-1), linux-compiler-gcc-4.8-x86:amd64(3.16.7-1, 3.16.7-2), linux-doc-3.16:amd64(3.16.7-1, 3.16.7-2), linux-headers-3.16.0-4-amd64:amd64 (3.16.7-1, 3.16.7-2), linux-headers-3.16.0-4-common:amd64 (3.16.7-1, 3.16.7-2), linux-image-3.16.0-4-amd64:amd64(3.16.7-1, 3.16.7-2), linux-libc-dev:amd64(3.16.7-1, 3.16.7-2), linux-support-3.16.0-4:amd64(3.16.7-1, 3.16.7-2), locales-all:amd64 (2.19-12, 2.19-13), locales:amd64 (2.19-12, 2.19-13), multiarch-support:amd64 (2.19-12, 2.19-13), netpbm:amd64(10.0-15.1+b1, 10.0-15.2), openjdk-7-demo:amd64(7u71-2.5.3-1, 7u71-2.5.3-1+b1), openjdk-7-jdk:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), openjdk-7-jre-headless:amd64(7u71-2.5.3-1, 7u71-2.5.3-1+b1), openjdk-7-jre:amd64 (7u71-2.5.3-1, 7u71-2.5.3-1+b1), wget:amd64 (1.16-2, 1.16-3), End-Date: 2014-11-07 11:39:36 -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#768480: lincity-ng: Start Up Causes Black Screen After Booting Latest Kernel
On 14Nov07:1912+0100, Markus Koschany wrote: I don't believe this is related to lincity-ng because the game has not been updated for quite some time, but rather to a change in the kernel or your nouveau drivers. I can confirm that lincity-ng works with the free radeon drivers on my system. I agree--lincity was fine yesterday. The morning update seriously changed something in lincity's environment. There are a lot of search hits for failed to idle channel 0x that indicate that this might be a driver issue. None within the last week save this one, though. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#768480: lincity-ng: Start Up Causes Black Screen After Booting Latest Kernel
I noticed these two for linux-image-3.16: #768452 system locks up every one or two days since upgrade to kernel 3.16 #768483 system freeze, usually on kernel upgrade or resume from hibernate that appear to be similar--can this bug be transferred to their queue? -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#768480: Megaglest Test, Part 1
On 14Nov07:2142+0100, Markus Koschany wrote: What happens if you try to play other games such as megaglest, foobillardplus or cube2-data? I installed megaglest which pulled in famfamfam-flag-png, fonts-uralic, libftgl2, libircclient1, libminiupnpc10, libxerces-c3.1, and megaglest-data without incident. After launching megaglest from the Games menu, the screen blacked, then after several seconds became a pattern of tiles about 10x50px each, and they were paired with the right side being a mirror of the left side in each instance; mostly grey with some deep blue. After a matter of minutes, startx ended, and the log showed a segfault had occurred. There were two of the nouveau messages concerning X, then there were four for chromium that were issued after X had perished. I noticed VC painting was quite slow while this was going on (as it had for the lincity instance) but it reverted to normal speed after X was gone. I restarted startx and the initial screen game up tiled as it had after launching megaglest. Ctl-Alt-BS appeared to be a no-op. After pressing Ctl-Alt_F2, it was ten seconds before the VC manifested on the screen and painting was slow. An Alt-F1 took ten seconds to produce a black screen with an X pointer, then startx terminated again (another segfault). I'll try a reboot after I mail this account. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#768480: Megaglest Test, Part 2
After the reboot, XFCE came up nominally. Launching megaglest also came up nominally, as did lincity-ng. I will attempt to determine how intermittent the problem is with a bunch of reboots for a while, then uninstall all the megaglest software and do a bunch more reboots. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#768480: Megaglest Test, Reboot Tests
I did ten reboots with megaglest installed. The first five were nominal, the 7th never got to VC login prompt after all the boot/init messages stopped and the screen cleared, and the rest failed as previously reported. I then uninstalled the megaglest packages and started reboot test again. Except for the 6th, which failed as reported, the first were all nominal. Then a string of (so far) six failures manifested. Using a VC to kill the lincity-ng process, I noticed the lock-outs were not always manifesting, but seemed to come in a few second long groups associated with a nouveau complaint. In one test I received a notice: [sched_delayed] sched: RT throttling activated while locked out. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#763148: Prevent migration to jessie
On 14Oct05:2254+0200, Andreas Barth wrote: Also, the re-evaluation happened. It however didn't had the outcome you wanted (basically because the web browser needs so many security updates which only could be done by backporting all of it that the embedded copy doesn't make any difference - this is an exceptional thing which does happen but not very often. I can understand it, and of course it's the call of the security team how to ensure that Debian has security updates. I hadn't know that at the time I though about the possibility, otherwise I would have already achived at that moment at the conclusion). Where are the minutes of the re-evaluation? -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#763287: Works in a Virtual Machine
I built a virtual machine, installed D-I Beta 1 netinst with no additional software, performed a full-upgrade to Sid, and installed a minimum configuration virt-manager and task-xfce-desktop with no auto-recommends, and the GUI does not manifest the issues previously observed. I would think this problem therefore has nothing to do with virt-manager. As the problem manifests with an XFCE environment, this bug should to handed off to them or closed and I'll open a new bug--your choice. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#763287: virt-manager: Update broke radio buttons--cannot tell what's selected
Package: virt-manager Version: 1:1.0.1-2 Severity: important Dear Maintainer, After my daily Sid update which upgraded virt-manager among others, the windows are laid out differently, and radio buttons and checkboxes immediately lose any contents. It is almost impossible to create a new virtual machine as it currently stands. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gconf2 3.2.6-3 ii gir1.2-gtk-3.0 3.14.0-1 ii gir1.2-gtk-vnc-2.0 0.5.3-1.2 ii gir1.2-libvirt-glib-1.0 0.1.7-2.1 ii gir1.2-spice-client-gtk-3.0 0.25-1 ii gir1.2-vte-2.90 1:0.36.3-1 ii librsvg2-common 2.40.4-1 ii python-dbus 1.2.0-2+b3 ii python-gi3.14.0-1 ii python-gi-cairo 3.14.0-1 ii python-ipaddr2.1.11-2 ii python-libvirt 1.2.8-1 ii python-urlgrabber3.9.1-4 pn python2.7:anynone pn python:any none ii virtinst 1:1.0.1-2 Versions of packages virt-manager recommends: ii gnome-icon-theme 3.12.0-1 ii libvirt-daemon 1.2.8-2 ii python-spice-client-gtk 0.25-1 Versions of packages virt-manager suggests: ii gnome-keyring3.14.0-1 ii python-gnomekeyring 2.32.0+dfsg-3 ii python-guestfs 1:1.26.9-1 ii ssh-askpass 1:1.2.4.1-9 ii virt-viewer 0.6.0-1 -- no debconf information -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#763287: Ignore Original Email Address
Odd--reportbug asked for and received my current email address, yet From: went out with the old and non-existent address. Please use the email address for this addition. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep24:1951+0200, Michael Biebl wrote: Am 24.09.2014 um 18:45 schrieb Michael Biebl: Craig was so kind and provided me with access to the VM images. With that image I was able to reproduce the upgrade failure. I checked the systemd state before the upgrade and noticed that sstemd-logind.service had failed to start due to dbus not being installed. So I made a second test-upgrade and I installed the dbus package beforehand. With dbus being installed and dbus.service running, the dist-upgrade was successful. There might be an issue with the internal dbus socket, that systemd uses for communication. My guess is, that with dbus.service running, it can fall back to the system bus for communication in case there is something wrong with that internal dbus socket. One more observation: The udev package is configured before systemd, i.e. udev.postinst runs before systemd.postinst (systemd.postinst run daemon-reexec). The restart of udev (invoke-rc.d udev restart) is what's failing. I tried it manually via root@vp9cb:~# systemctl restart udev.service Failed to wait for response: Success If I manually reexec systemd via systemctl daemon-reexec, I can successfully finish the dist-upgrade via dpkg --configure -a and apt-get -f install Full typescript attached Maybe I should be a full-time tester--I seem to be pretty good at it. I built another vm from the D-I beta, pointed sources.list at sid, and ran aptitude update, all as before. This time, though, I held all updates while installing dbus 1.8.8-1 and libcap-ng0 0.7.4-2 with nominal results, then unheld the updates again (aptitude : if it matters) and ran the aptitude dist-upgrade, which failed as before. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep24:1424-0400, David L. Craig wrote: Maybe I should be a full-time tester--I seem to be pretty good at it. I built another vm from the D-I beta, pointed sources.list at sid, and ran aptitude update, all as before. This time, though, I held all updates while installing dbus 1.8.8-1 and libcap-ng0 0.7.4-2 with nominal results, then unheld the updates again (aptitude : if it matters) and ran the aptitude dist-upgrade, which failed as before. Then I reran the entire test except I added a reboot after the apt-get install dbus and, even though the download of libdbus-1-3 failed, the rest of the dist-upgrade was fine. So I perceive the start of the dbus.service is not automatic. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:0023+0200, Michael Biebl wrote: Yeah, this would be perfect By way of a feasibility test, I had virt-manager Shut Down == Save the a762146 vm at its ready for first login state and have put the tarball of the 124MB file it created in /var/lib/libvirt/qemu/save up at http://dlc.casita.net/~dlc/762146/a762146.vmsave.test.tar for you to retrieve. I expect you will also need the hard drive image which compressed into 5.3 GB, so we have a logistical difficulty there. I am attaching the domain xml and parted print free output in sectors for the virtual disk. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ a762146.xml.tar Description: Unix tar archive Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 4096s Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start EndSize File system Name Flags 34s2047s 2014s Free Space 1 2048s 3905535s 3903488s linux-swap(v1) VS 2 3905536s 40957951s 37052416s ext4VV 40957952s 40959966s 2015s Free Space signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:0956-0400, David L. Craig wrote: By way of a feasibility test, I had virt-manager Shut Down == Save the a762146 vm at its ready for first login state and have put the tarball of the 124MB file it created in /var/lib/libvirt/qemu/save up at http://dlc.casita.net/~dlc/762146/a762146.vmsave.test.tar for you to retrieve. I expect you will also need the hard drive image which compressed into 5.3 GB, so we have a logistical difficulty there. I am attaching the domain xml and parted print free output in sectors for the virtual disk. Scratch that--those files were taking up too much space. Instead, I offer you an invitation to send me an encrypted email to which I will likewise reply with the details of how to SFTP the files (522MB, but you should get at least 4 MB/sec bandwidth from this end) for the actual vm condition you requested (even better--I did an aptitude --download-only --dist-upgrade prior to the save). Also, I ran it beforehand in the constrained configuration (1 GB root, no swap) to ensure this fails identically, and it obliged me. I hope this works, er, you can get a successful test. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
Another datum: I decided to try switching back to systemd-sysv on my primary bare-metal Sid and the update was textbook: ii libpam-systemd:amd64 215-4 ii libsystemd-id128-0:amd64 215-4 ii libsystemd-journal0:amd64 215-4 ii libsystemd-login0:amd64 215-4 ii libsystemd-login0:i386215-4 ii libsystemd0:amd64 215-4 ii libsystemd0:i386 215-4 ii systemd 215-4 ii systemd-shim 8-2 ii systemd-sysv 215-4 ii systemd-ui3-2 -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:1719-0400, David L. Craig wrote: Another datum: I decided to try switching back to systemd-sysv on my primary bare-metal Sid and the update was textbook: ii libpam-systemd:amd64 215-4 ii libsystemd-id128-0:amd64 215-4 ii libsystemd-journal0:amd64 215-4 ii libsystemd-login0:amd64 215-4 ii libsystemd-login0:i386215-4 ii libsystemd0:amd64 215-4 ii libsystemd0:i386 215-4 ii systemd 215-4 ii systemd-shim 8-2 ii systemd-sysv 215-4 ii systemd-ui3-2 So I tried running the test case on the bare metal again, but it still fails. :-( -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep21:2011+0200, Michael Biebl wrote: What were the exact error messages you got? Please provide the dpkg log and the output from journalctl -alb I ran the test case again and obtained the same results from aptitude dist-upgrade and began receiving the kernel messages about journald as well; however, the system performed a telinit 6 nominally after I had executed your requested journalctl -alb redirecting stdout and stderr to a file. When in single user mode, did you also try to run dpkg --configure -a or apt-get -f install to fix the broken package state? While dpkg --configure -a complained about nothing, acl and systemd remained broken; however, apt-get -f install was successful. Attached are the dpkg and apt logs. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ a762146.journalctl-alb.out.gz Description: application/gzip a762146.dpkg.log.gz Description: application/gzip a762146.apt-term.log.gz Description: application/gzip a762146.apt-history.log.gz Description: application/gzip signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:0016+0200, Michael Biebl wrote: Am 22.09.2014 um 23:23 schrieb David L. Craig: On 14Sep21:2011+0200, Michael Biebl wrote: What were the exact error messages you got? Please provide the dpkg log and the output from journalctl -alb I ran the test case again and obtained the same results from aptitude dist-upgrade and began receiving the kernel messages about journald as well; however, the system performed a telinit 6 nominally after I had executed your requested journalctl -alb redirecting stdout and stderr to a file. I wasn't able to reproduce the failure. Would it be possible for you to create a VM image I can download? Hmmm... Probably, once I figure out how. You want it just before the dist-upgrade command? -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep22:0005+0200, Michael Biebl wrote: Am 21.09.2014 um 23:28 schrieb David L. Craig: No, but, as the report mentioned, the vm failure was preceded by a similar result doing the daily update of the main non-vm Sid instance on the box, which is why I reproduced it using reproducible and minimal inputs. Are you too resource-challenged to run it yourselves? No, I've done dozens of test-upgrades on bare metal and VMs (vbox, vmware) and haven't run into this. So we either need someone who can reproduce the problem or exact steps how to reproduce it. It seems most likely to me the difference will be found in the processor, or perhaps its firmware. The box is from Gigabyte but it's configured for reliability, not speed. The work-in-process cookbook I've been putting together will walk you through what was being done with screenshots in case that is useful information. I put the current document snapshot up for this bug. You can download the 35 MB tarball from http://dlc.casita.net/~dlc/762146/vp9cb-20140921.tar or just click through the HTML by going to http://dlc.casita.net/~dlc/762146/vp9cb/index.html and see what happened in subsection 2-3. Let me know if there is a specific test case you want me to exercise and I'll do my best to get you the data. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
Package: udev Version: 215-4 Severity: grave Installed Beta 1 D-I amd64 netinst without mirror or standard utils in preparation for dist-upgrade to Sid using aptitude with sources.list: deb ftp://debian.csail.mit.edu/debian/ sid main udev and aptitude reported replacing 208-6. udev fails first during configure after systemd incurs systemd-journald.service watchdog timeout! Next systemd fails to configure, then cron does the same. At the conclusion of dist-upgrade, all three are broken and reportbug cannot be force installed. In single, used aptitude to uninstall systemd-sysv and install systemd-shim, enabling all other updates to install nominally. Platform is a virtual machine under current Sid using qemu and kvm on a quad-core Intel. That system incurred a similar outcome from its daily update roughly 12 hours previously and recovered with the same remediation used for the virtual machine. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
Correction: udev and systemd reported replacing 208-6. ^^^ not aptitude -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#729203: Still Not Uploaded
Having discovered this bug report and subsequently absorbing it, I cloned the repository, built the debs, and installed them into my primary Sid box. Now I need to track the repo. I didn't see why this package has still not been uploaded. Perhaps I need to reread the report. Nonetheless, all the objections to the state of ffmpeg in Debian remain unaddressed. This is, to me, egregious. Even if ffmpeg is the only project to be so abused by Debian, that by itself is sufficient to discredit the distribution as a whole. The value-add of all the members of the team can be rendered useless for some installations by the handling of even one important component. Having begun with release 1.0^H1 so long ago, I may have arrived at the point of looking elsewhere for my primary GNU/Linux distro. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#720191: avahi-utils: avahi-resolve does not find a published host
Package: avahi-utils Version: 0.6.31-2 Severity: important Tags: ipv6 I'm trying to use mdns naming accross a virtual ethernet link between a Debian 32-bit guest and a RHEL6 64-bit host, both running 'avahi-daemon'. Resolution with other programs also doesn't work, but I've done the most analysis with 'avahi-resolve'. Command line... dllamber@vmDebian:/usr/share/java$ avahi-resolve -4 -n oc3676843524.LOCAL Failed to resolve host name 'oc3676843524.LOCAL': Timeout reached 'tcpdump' output during the first couple seconds (before the 'Timeout reached' message appears)... vmDebian:/home/dllamber# tcpdump -i eth0 -ttt -vv udp port 5353 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 00:00:00.00 IP6 (hlim 255, next-header UDP (17) payload length: 44) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0 A (QM)? oc3676843524.LOCAL. (36) 00:00:00.000148 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 64) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum a747!] 0 A (QM)? oc3676843524.LOCAL. (36) 'tcpdump' output thereafter... 00:00:00.000531 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 74) oc3676843524.1028 224.0.0.251.mdns: [udp sum ok] 0*- [0q] 1/0/0 oc3676843524.local. (Cache flush) A 192.168.122.1 (46) 00:00:00.101370 IP6 (hlim 255, next-header UDP (17) payload length: 98) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0 PTR (QM)? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90) 00:00:00.000164 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 118) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum c029!] 0 PTR (QM)? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90) 00:00:00.899400 IP6 (hlim 255, next-header UDP (17) payload length: 44) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0 A (QM)? oc3676843524.LOCAL. (36) 00:00:00.000150 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 64) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum a747!] 0 A (QM)? oc3676843524.LOCAL. (36) 00:00:00.000224 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 74) oc3676843524.1028 224.0.0.251.mdns: [udp sum ok] 0*- [0q] 1/0/0 oc3676843524.local. (Cache flush) A 192.168.122.1 (46) 00:00:00.100438 IP6 (hlim 255, next-header UDP (17) payload length: 98) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0 PTR (QM)? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90) 00:00:00.000224 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 118) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum c029!] 0 PTR (QM)? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (90) 00:00:01.901520 IP6 (hlim 255, next-header UDP (17) payload length: 122) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0 [2q] A (QM)? oc3676843524.LOCAL. PTR (QM)? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (114) 00:00:00.000220 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 142) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum 67d4!] 0 [2q] A (QM)? oc3676843524.LOCAL. PTR (QM)? b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa. (114) 00:00:00.000423 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 74) oc3676843524.1028 224.0.0.251.mdns: [udp sum ok] 0*- [0q] 1/0/0 oc3676843524.local. (Cache flush) A 192.168.122.1 (46) 00:00:02.097754 IP6 (hlim 255, next-header UDP (17) payload length: 98) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0 PTR (QM)? 3.6.5.8.e.9.e.f.f.f.9.2.c.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90) 00:00:00.000176 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 118) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum b828!] 0 PTR (QM)? 3.6.5.8.e.9.e.f.f.f.9.2.c.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (90) 00:00:00.000283 IP6 (hlim 255, next-header UDP (17) payload length: 120) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0*- [0q] 1/0/0 3.6.5.8.e.9.e.f.f.f.9.2.c.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (Cache flush) PTR vmDebian.local. (112) 00:00:00.001031 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 140) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum 9835!] 0*- [0q] 1/0/0 3.6.5.8.e.9.e.f.f.f.9.2.c.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (Cache flush) PTR vmDebian.local. (112) 00:00:00.100613 IP6 (hlim 255, next-header UDP (17) payload length: 50) vmDebian.local.mdns ff02::fb.mdns: [udp sum ok] 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42) 00:00:00.000226 IP (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 70) vmDebian.mdns 224.0.0.251.mdns: [bad udp cksum 2f19!] 0 PTR (QM)? 251.0.0.224.in-addr.arpa. (42) 00:00:01.000666 IP6 (hlim 255, next-header UDP (17) payload length:
Bug#703235: Error In Initial Report Text
The final two commands reported begin with './waf', not '../waf'; i.e., the actual commands executed agree with the cookbook, not the bug report). -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#684952: linux rt 3.4.8-rt16 and nv 302.17, and system freezes, does nvidia strike again?
On 12Aug23:2032-0400, David L. Craig wrote: On 12Aug23:1850-0400, David L. Craig wrote: I'm looking at the nvidia forum's guidelines for reporting bugs and will let you know what I determine to do. There being no obvious comparable existing report, I opened http://www.nvnews.net/vbulletin/showthread.php?p=2571517#post2571517 which points to the Debian report (684952) for all details. Now we wait again. -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684952: nvidia-glx: startx blackens screen, keyboard ineffective save for altSysReq
On 12Aug15:1037+0200, Andreas Beckmann wrote: On 2012-08-15 09:48, David L. Craig wrote: I updated all the nvidia packages when I saw the new versions but the problem persists. I am including the most recent kern.log Kernel: Linux 3.2.0-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Please try the non-rt kernel. That is working, albeit differently than under Linux Mint XFCE 13. Please try a minimal xorg.conf as described in /usr/share/doc/nvidia-glx/README.Debian.gz and test using a single display without twinview first. If that works, slowly add more options (if you need them). That option was necessary to get nvidia to work under Mint. It causes a problem under Sid with 3.2.0-3-rt-amd64 and 3.2.0-3-amd64. 3.2.0-3-amd64 works with 1024x768 but not with 1152x864. However, I had to comment-out my console-setup VGA 8x8 defaults because nvidia doesn't show all 50 lines as nouveau does. Where is that dark magic documented? 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV43 [GeForce 6600] [10de:0141] (rev a2) (prog-if 00 [VGA controller]) That's an old card that should also work with nvidia-glx-legacy-173xx Do you want me to explore the behavior of nvidia-glx-legacy-173xx? What was the last working version? Appended is hopefully sufficient diagnostic information about the Mint environment. If nothing of the above helps, Nvidia's bug reporting instructions are here: http://www.nvnews.net/vbulletin/showthread.php?t=46678 Please post a link to a thread in their forum to this Debian bug. I'm a tad confused. Is 3.2.0-3-rt-amd64 unsupported by nVidia or Debian? That is, should I report the rt bug there or not? Andreas Thank you so much for your support of this software!!! -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ # dlc@dlc-dt[LMDX]~/Desktop $ uname -a Linux dlc-dt 3.2.0-23-lowlatency #31-Ubuntu SMP PREEMPT Wed Apr 11 02:24:03 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux dlc@dlc-dt[LMDX]~/Desktop $ ll /usr/lib/nvidia-current /lib/nvidia-current /lib/nvidia-current: total 12K drwxr-xr-x 2 root root 4.0K Jul 26 17:37 ./ drwxr-xr-x 22 root root 4.0K Jul 26 19:59 ../ -rw-r--r-- 1 root root 316 Apr 12 15:15 modprobe.conf /usr/lib/nvidia-current: total 72M drwxr-xr-x 6 root root 4.0K Jul 26 17:37 ./ drwxr-xr-x 217 root root 52K Aug 2 02:26 ../ -rw-r--r-- 1 root root 27 Apr 12 15:15 XvMCConfig -rw-r--r-- 1 root root0 Apr 12 15:15 alt_ld.so.conf drwxr-xr-x 2 root root 4.0K Jul 26 17:37 bin/ -rw-r--r-- 1 root root 50 Apr 12 15:15 ld.so.conf lrwxrwxrwx 1 root root 10 Apr 12 15:15 libGL.so - libGL.so.1 lrwxrwxrwx 1 root root 15 Apr 12 15:15 libGL.so.1 - libGL.so.295.40 -rw-r--r-- 1 root root 1.1M Apr 12 15:15 libGL.so.295.40 lrwxrwxrwx 1 root root 14 Apr 12 15:15 libOpenCL.so - libOpenCL.so.1 lrwxrwxrwx 1 root root 16 Apr 12 15:15 libOpenCL.so.1 - libOpenCL.so.1.0 lrwxrwxrwx 1 root root 18 Apr 12 15:15 libOpenCL.so.1.0 - libOpenCL.so.1.0.0 -rw-r--r-- 1 root root 21K Apr 12 15:15 libOpenCL.so.1.0.0 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libXvMCNVIDIA.so - libXvMCNVIDIA.so.295.40 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libXvMCNVIDIA.so.1 - libXvMCNVIDIA.so.295.40 -rw-r--r-- 1 root root 156K Apr 12 15:15 libXvMCNVIDIA.so.295.40 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libXvMCNVIDIA_dynamic.so.1 - libXvMCNVIDIA.so.295.40 lrwxrwxrwx 1 root root 17 Apr 12 15:15 libcuda.so - libcuda.so.295.40 lrwxrwxrwx 1 root root 17 Apr 12 15:15 libcuda.so.1 - libcuda.so.295.40 -rw-r--r-- 1 root root 8.3M Apr 12 15:15 libcuda.so.295.40 lrwxrwxrwx 1 root root 15 Apr 12 15:15 libnvcuvid.so - libnvcuvid.so.1 lrwxrwxrwx 1 root root 20 Apr 12 15:15 libnvcuvid.so.1 - libnvcuvid.so.295.40 -rw-r--r-- 1 root root 2.2M Apr 12 15:15 libnvcuvid.so.295.40 lrwxrwxrwx 1 root root 18 Apr 12 15:15 libnvidia-cfg.so - libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libnvidia-cfg.so.1 - libnvidia-cfg.so.295.40 -rw-r--r-- 1 root root 134K Apr 12 15:15 libnvidia-cfg.so.295.40 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libnvidia-compiler.so - libnvidia-compiler.so.1 lrwxrwxrwx 1 root root 28 Apr 12 15:15 libnvidia-compiler.so.1 - libnvidia-compiler.so.295.40 -rw-r--r-- 1 root root 27M Apr 12 15:15 libnvidia-compiler.so.295.40 -rw-r--r-- 1 root root 34M Apr 12 15:15 libnvidia-glcore.so.295.40 lrwxrwxrwx 1 root root 17 Apr 12 15:15 libnvidia-ml.so - libnvidia-ml.so.1 lrwxrwxrwx 1 root root 22 Apr 12 15:15 libnvidia-ml.so.1 - libnvidia-ml.so.295.40 -rw-r--r-- 1 root root 243K Apr 12 15:15 libnvidia-ml.so.295.40 -rw-r--r-- 1 root root 12K Apr 12 15
Bug#684952: nvidia-glx: startx blackens screen, keyboard ineffective save for altSysReq
Package: nvidia-glx Version: 302.17-3 Severity: critical Justification: breaks the whole system I had installed Sid into an available partition and X was happy with nouveau. nvidia was functioning well under Linux Mint Xfce 13. After installing the nvidia packages and porting the Mint xorg.conf into /etc/X11, I found I had a guaranteed to manifest problem. After dozens of tests and changes, it is clear the impact is to more than just the keyboard/monitor (ssh sessions receive some setterm -msg on -msglevel 8 outputs) but altSysReq REISUB doesn't provide much diagnostic output. Mint works using 1152x864, Sid works with neither that or 1024x768. -- Package-specific info: uname -a: Linux dlc-dt 3.2.0-3-rt-amd64 #1 SMP PREEMPT RT Mon Jul 23 03:37:45 UTC 2012 x86_64 GNU/Linux /proc/version: Linux version 3.2.0-3-rt-amd64 (Debian 3.2.23-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP PREEMPT RT Mon Jul 23 03:37:45 UTC 2012 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 302.17 Tue Jun 12 16:03:22 PDT 2012 GCC version: gcc version 4.6.3 (Debian 4.6.3-8) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV43 [GeForce 6600] [10de:0141] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Device [196e:021f] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f000 (32-bit, non-prefetchable) [size=64M] Region 1: Memory at e000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f600 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at f400 [disabled] [size=128K] Capabilities: access denied Kernel driver in use: nvidia dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.00] Console: colour VGA+ 80x25 [0.474228] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.474228] vgaarb: loaded [0.474228] vgaarb: bridge control possible :01:00.0 [0.984332] Linux agpgart interface v0.103 [7.365727] nvidia: module license 'NVIDIA' taints kernel. [7.567856] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [7.567863] nvidia :01:00.0: setting latency timer to 64 [7.567870] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [7.567993] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 302.17 Tue Jun 12 16:03:22 PDT 2012 OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Aug 13 21:00 /etc/alternatives/glx - /usr/lib/nvidia lrwxrwxrwx 1 root root 43 Aug 13 21:00 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Aug 13 21:00 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 59 Aug 13 21:00 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Aug 13 21:00 /etc/alternatives/glx--linux-libglx.so - /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 36 Aug 13 21:00 /etc/alternatives/glx--nvidia-bug-report.sh - /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Aug 13 21:00 /etc/alternatives/glx--nvidia_drv.so - /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 23 Aug 13 21:00 /etc/alternatives/nvidia - /usr/lib/nvidia/current lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 59 Aug 13 21:00 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 67 Aug 13 21:00 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 33 Aug 13 21:00 /etc/alternatives/nvidia--libglx.so - /usr/lib/nvidia/current/libglx.so lrwxrwxrwx 1 root root 59 Aug 13 21:00
Bug#673203: Hmmm... Maybe
Maybe it's time to become a DD. I've been unable to scare up a job in IT for a long time now so maybe it's time to plan to just live on Social Security benefits (if you call that living) and invest my copious free time into the community. I started with Debian at version 1.0^H1 (Linux Counter number 2419) and have been using Audacity and a little Ardour and JACK, but not much snd. I'm mostly an OS internals kind of guy. Website at http://www.radix.net/~dlc if you're interested. At the moment I just got my hand-me-down Gigabyte Intel quad-core 8 GB box with a GeForce 6600 NV43 adapter upgraded to Linux Mint XFCE Maya with the nvidia driver and was starting to look at building Wheeze from source optimized for performance in another partition. I also have an Acer Aspire One 1 GB Atom netbook about to get the Maya treatment. What do you think about me getting involved with maintaining the snd debs? How much time do you think this is going to require? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566735: grub-pc: Unable to boot from LVM, error: no such disk.
Vladimir 'φ-coder/phcoder' Serbinenko wrote: Could you try booting from external media and see how much sectors of hd0 does the GRUB see? BIOS may not present the entire disk to the bootloader. If it's so and the disk is ATA you can workaround it with: grub-install --disk-module=ata /dev/sda I looked but I couldn't find a way for GRUB to say how many sectors it sees. What is the command? I tried --disk-module=ata and now I get error: device not connected. and then the menu appears. My LVM partitions are recognized and I'm able to boot Linux. So it looks like this workaround solves the problem. I think you can close this bug. Thanks for your patience and your help! Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621360: [php-maint] Bug#621360: /etc/cron.d/php5 wreaks havoc on session-based PHP apps
No, I understand the concept of the cron job. I do agree that allowing PHP/Apache to enumerate the session directory is a bad idea. Seems like PHP's session garbage collection is lacking a bit. Surely they could devise a means of garbage collection that doesn't relay on scanning a directory. I see that bug #590485 fixes the cron job so I can use conf.d to override. So I could just override the global defaults by having my sugarcrm package install a config file fragment. Thanks for taking the time to look at this! David L Norris Manager of Information Technology DKI Services Corporation dnor...@dkiservices.com Direct: 317.614.0298 Mobile: 317.417.1188 Fax: 317.481.8984 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566735: grub-pc: Unable to boot from LVM, error: no such disk.
David L. Anselmi wrote: Vladimir 'φ-coder/phcoder' Serbinenko wrote: Could you supply the dump of first 64K of you PV? Here it is, sorry for the delay. Dave pv.bin.bz2 Description: Binary data
Bug#566735: grub-pc: Unable to boot from LVM, error: no such disk.
Vladimir 'φ-coder/phcoder' Serbinenko wrote: Could you supply the dump of first 64K of you PV? Sure. I'll send it as soon as I get a chance. I noticed that maybe a working grub2 (on AMD64) had more modules loaded than the non-working (i386) grub2. But grub.cfg is essentially the same on both and I haven't had time to try to reproduce the difference. Thanks! Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566735: grub-pc: Unable to boot from LVM, error: no such disk.
Package: grub-pc Version: 1.98+20100804-4 Severity: normal I've retested and this bug still exists so I'll reopen. Here's the new behavior. On boot it says: error: no such disk Entering rescue mode grub rescue (i.e., only one error line rather than two). lsmod shows: NameRef Count Dependencies lvm 1 part_msdos 1 ext21 fshelp fshelp 2 biosdisk1 minicmd 1 and ls: (hd0) (hd0,msdos2) (hd0,msdos1) (fd0) So I think I have a correct config and the right modules, but something doesn't work. From the grub prompt is there anything else I can do to troubleshoot? root seems not to be usable, even if I set it to vg0-root. I don't think there is anything unusual about this disk. The first partition is NTFS, the second is LVM. I have a 32 bit box with a single LVM partition and grub2 works fine. I have a 64 bit box with more complicated partitions and grub2 works fine. I suppose the LVM partition might be pretty old--could it be not quite right for grub2? I don't get any errors when looking at the pvs/vgs/lvs. How else can I help? Thanks! Dave -- Package-specific info: *** BEGIN /proc/mounts /dev/mapper/vg0-root / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/mapper/vg0-home /home ext3 rw,relatime,errors=continue,data=ordered 0 0 /dev/mapper/vg0-tmp /tmp ext3 rw,relatime,errors=continue,data=ordered 0 0 /dev/mapper/vg0-usr /usr ext3 rw,relatime,errors=continue,data=ordered 0 0 /dev/mapper/vg0-var /var ext3 rw,relatime,errors=continue,data=ordered 0 0 /dev/mapper/vg0-audio /srv/audio ext3 rw,relatime,errors=continue,data=ordered 0 0 /dev/mapper/vg0-debian /srv/debian ext3 rw,relatime,errors=continue,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (hd0) /dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10Y429365 *** END /boot/grub/device.map -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages grub-pc depends on: ii debconf [debconf-2.0]1.5.32 Debian configuration management sy ii grub-common 1.98+20100804-4 GRand Unified Bootloader, version ii libc62.10.2-9Embedded GNU C Library: Shared lib ii libdevmapper1.02.1 2:1.02.45-1 The Linux Kernel Device Mapper use ii ucf 3.0025 Update Configuration File: preserv grub-pc recommends no packages. Versions of packages grub-pc suggests: ii desktop-base 5.0.5 common files for the Debian Deskto -- debconf information: grub2/kfreebsd_cmdline: * grub2/device_map_regenerated: * grub2/linux_cmdline: grub-pc/install_devices_empty: false grub-pc/install_devices_failed: false grub-pc/chainload_from_menu.lst: true grub-pc/kopt_extracted: false * grub-pc/install_devices: /dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10Y429365 grub-pc/postrm_purge_boot_grub: false grub-pc/install_devices_failed_upgrade: true grub-pc/disk_description: grub2/kfreebsd_cmdline_default: quiet grub-pc/partition_description: grub-pc/install_devices_disks_changed: * grub2/linux_cmdline_default: quiet grub-pc/mixed_legacy_and_grub2: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566735: grub-pc: Unable to boot from LVM, error: no such disk.
do you have a LVM snapshot by any chance? If yes you could be hit by Bug #574863. No, I don't have any snapshots. I'll try a newer version and report the results. Sorry, I didn't respond because I wasn't cc'd by Bernhard. Thanks! Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598804: Fwd: Knoppix Worked
Apparently this addendum never was received or accepted. -- Forwarded message -- From: David L. Craig dlc@gmail.com Date: Sun, Oct 3, 2010 at 6:47 PM Subject: Knoppix Worked To: 598...@bugs.debian.org I built a USB-ZIP format Knoppix-Live stick with V6.2.1 (Jan2010) which boots up without any problems. -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' __--from_Nightfall_by_Asimov/Silverberg
Bug#598804: Daily Boot Image Yields Dead Keyboard
Package: installation-reports Boot method: How did you boot the installer? CD? floppy? network? USB-stick Image version: Full URL to image you downloaded is best http://people.debian.org/~joeyh/d-i/images/daily/hd-media/boot.img.gz Date: Date and time of the install Image downloaded at 04:51 UTC 02 Oct 2010 Machine: Description of machine (eg, IBM Thinkpad R32) Acer Aspire one 532h-2789 Processor: Atom N450 Memory: 1 GB Partitions: df -Tl will do; the raw partition table is preferred N/A (floppy image) Output of lspci -knn (or lspci -nn): N/A Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[E] Comments/Problems: After displaying initial option screen, keystrokes are ignored Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' __--from_Nightfall_by_Asimov/Silverberg_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569524: linux-image-2.6.26-2-686: cannot mount ext2 fs created by 2.6.30 but fsck is clean
On Fri, Feb 12, 2010 at 09:26:25AM +0100, Bastian Blank wrote: tags 569524 moreinfo thanks No, thank YOU! You probably don't want to think about how much this would be costing me if you were working on this problem for the benefit of Microsoft versus how much _you_ would be getting. Any reason, why you did not check what exactly the kernel wants to tell you? Ignorance? What do I need to do to get it to spit out what would be helpful? large_file is marked as read-only compatible and supported since at least 2.6.12. muse:~# mount - -L _u1 -o ro mount: fstab path: /etc/fstab mount: lock path: /etc/mtab~ mount: temp path: /etc/mtab.tmp mount: going to mount LABEL=_u1 by LABEL mount: spec: /dev/sdc1 mount: node: /_/_ub mount: types: ext2 mount: opts: users,noamode,ro mount: mount(2) syscall: source: /dev/sdc1, target: /_/_ub, filesystemtype: ext2, mountflags: -1058209777, data: noamode mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so muse:~# [163648.720862] EXT3-fs: mounted filesystem with ordered data mode. [165778.814712] ext3: No journal on filesystem on sdd This is something completely different, it is no ext3. I believe I tried an ext3 definition to determine if that might mount. The first line cited refers to a different device. -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' __--from_Nightfall_by_Asimov/Silverberg_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569524: linux-image-2.6.26-2-686: cannot mount ext2 fs created by 2.6.30 but fsck is clean
On Fri, Feb 12, 2010 at 09:07:40AM -0500, David L. Craig wrote: On Fri, Feb 12, 2010 at 09:26:25AM +0100, Bastian Blank wrote: large_file is marked as read-only compatible and supported since at least 2.6.12. [*blush*] They mount fine when I change noamode to noatime, even rw. Clearly my IBM mainframe background is showing. Please close this problem and forget all about it (and me)... -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' __--from_Nightfall_by_Asimov/Silverberg_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569524: Assimilation
On Fri, Feb 12, 2010 at 04:36:09PM +, Debian Bug Tracking System wrote: On Fri, Feb 12, 2010 at 11:04:30AM -0500, David L. Craig wrote: [*blush*] They mount fine when I change noamode to noatime, even rw. Clearly my IBM mainframe background is showing. Please close this problem and forget all about it (and me)... Closing, but maybe its better to assimilate you. Knowledge in IBM mainframes accompanied with linux knowledge is not that common and, well, Debian works there. Well, I'd love to, but I can't commit the time until I no longer have to work to support myself. As retirement now seems impossible, the only way I could do it would be for IBM to pay me to do it. That seems to be a Catch 22 scenario since they want documented kernel hacking chops on state-of-the-art hardware before they'll consider anything like that. Captain Kirk, I _shall_ consider it... --alternative Spock, episode and stardate not immediately available -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ 'So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe.' __--from_Nightfall_by_Asimov/Silverberg_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566735: grub-pc: Unable to boot from LVM, error: no such disk.
Package: grub-pc
Version: 1.98~20100101-1
Severity: important
Hi,
I'm unable to get grub-pc to boot. When installed it says this on boot:
error: no such disk
Entering rescue mode
error: no such disk
and gives me a rescue prompt. By running grub-install --modules=minicmd I could
see this:
lsmod:
lvm
part_msdos
ext2
fshelp
biosdisk
minicmd
ls:
(hd0) (hd0,2) (hd0,1) (fd0)
So it looks like grub can't see the LVM partitions.
I have a similar system that works fine with grub2. What can I do to figure out
why LVM doesn't show up?
Thanks!
Dave
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/vg0-root / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vg0-home /home ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/mapper/vg0-tmp /tmp ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/mapper/vg0-usr /usr ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/mapper/vg0-var /var ext3 rw,relatime,errors=continue,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/sda
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
insmod lvm
insmod ext2
set root=(vg0-usr)
search --no-floppy --fs-uuid --set 0f91c483-e04d-4e47-94a3-f355ed87e822
if loadfont /share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
set locale_dir=/boot/grub/locale
set lang=
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod lvm
insmod ext2
set root=(vg0-usr)
search --no-floppy --fs-uuid --set 0f91c483-e04d-4e47-94a3-f355ed87e822
insmod png
if background_image /share/images/desktop-base/nightly-wallpaper.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, with Linux 2.6.32-trunk-686 {
insmod lvm
insmod ext2
set root=(vg0-root)
search --no-floppy --fs-uuid --set 538ef660-a731-49b9-a15b-e6e82e7e09b1
linux /boot/vmlinuz-2.6.32-trunk-686 root=/dev/mapper/vg0-root ro
quiet
initrd /boot/initrd.img-2.6.32-trunk-686
}
menuentry Debian GNU/Linux, with Linux 2.6.32-trunk-686 (recovery mode) {
insmod lvm
insmod ext2
set root=(vg0-root)
search --no-floppy --fs-uuid --set 538ef660-a731-49b9-a15b-e6e82e7e09b1
linux /boot/vmlinuz-2.6.32-trunk-686 root=/dev/mapper/vg0-root ro
single
initrd /boot/initrd.img-2.6.32-trunk-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry Microsoft Windows 2000 Professional (on /dev/hda1) {
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set 9c68a0da68a0b484
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0]1.5.28 Debian configuration management sy
ii grub-common 1.98~20100101-1 GRand Unified Bootloader, version
ii libc62.10.2-2GNU C Library: Shared libraries
ii ucf 3.0025 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
-- debconf information:
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: false
* grub-pc/install_devices: /dev/hda
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default: quiet
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544382: man page of traceroute lacked info of tracert
tracert is equivalent to traceroute -I This is significant because without it the user has no idea why: $ tracert example.com returns The specified type of tracerouting is allowed for superuser only. Thanks! Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552413: bacula-common-sqlite3: No database upgrade from version 10 to 11.
John Goerzen wrote: David L. Anselmi wrote: On upgrading to bacula 3.0 I was told my catalog was empty and should new tables be created. I said no. I had hoped that my old catalog would be upgraded automatically. You can fix that with something along the lines of echo .dump | sqlite2 bacula.db.sqlite2 | sqlite3 bacula.db.sqlite This is from memory; a better recipe is probably in the preinst for bacula-sqlite3. I will try to look into why this happened next week. Thanks for the quick response. Here's what's seemed to work (run as the bacula user in /var/lib/bacula): sqlite bacula.db.sqlite2 .dump \ | sed 's/ INTEGER UNSIGNED AUTOINCREMENT,/ INTEGER,/' \ | sqlite3 bacula.db /usr/share/bacula-director/update_sqlite3_tables Hope that helps anyone else with this problem. I'll try to look at the bacula-director-sqlite3.postinst to see what went wrong. Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552413: bacula-common-sqlite3: No database upgrade from version 10 to 11.
Package: bacula-common-sqlite3 Version: 3.0.2-3+b1 Severity: important On upgrading to bacula 3.0 I was told my catalog was empty and should new tables be created. I said no. I had hoped that my old catalog would be upgraded automatically. So I have an empty /var/lib/bacula/bacula.db and a large bacula.db.sqlite2. The release notes say to use the update_bacula_tables script but that doesn't seem to be included. I tried the script at: http://bacula.git.sourceforge.net/git/gitweb.cgi?p=bacula/bacula;a=blob;f=bacula/updatedb/update_sqlite3_tables_10_to_11.in;h=54a407d26f307bbf2c02f09e2f1f155cc57ba9ae;hb=HEAD but it doesn't recognize the bacula.db.sqlite2 file. Here's what changed during the update: [REMOVE, NOT USED] bacula-director-sqlite [REMOVE, NOT USED] sqlite [INSTALL, DEPENDENCIES] bacula-common-sqlite3 [INSTALL, DEPENDENCIES] bacula-director-sqlite3 [INSTALL, DEPENDENCIES] bacula-sd-sqlite3 [INSTALL, DEPENDENCIES] sqlite3 [REMOVE, DEPENDENCIES] bacula-sd-sqlite [UPGRADE] bacula 2.4.4-1 - 3.0.2-3 [UPGRADE] bacula-client 2.4.4-1 - 3.0.2-3 [UPGRADE] bacula-common 2.4.4-1 - 3.0.2-3+b1 [UPGRADE] bacula-console 2.4.4-1 - 3.0.2-3+b1 [UPGRADE] bacula-director-common 2.4.4-1 - 3.0.2-3+b1 [UPGRADE] bacula-fd 2.4.4-1 - 3.0.2-3+b1 [UPGRADE] bacula-sd 2.4.4-1 - 3.0.2-3+b1 [UPGRADE] bacula-server 2.4.4-1 - 3.0.2-3 Thanks! Dave -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages bacula-common-sqlite3 depends on: ii adduser 3.111 add and remove users and groups ii bacula-common 3.0.2-3+b1 network backup, recovery and verif ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii libc6 2.9-25 GNU C Library: Shared libraries ii libgcc1 1:4.4.1-4 GCC support library ii libsqlite3-0 3.6.18-1 SQLite 3 shared library ii libstdc++64.4.1-4The GNU Standard C++ Library v3 bacula-common-sqlite3 recommends no packages. Versions of packages bacula-common-sqlite3 suggests: pn bacula-docnone (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#216951: Apt-get (and aptitude) update fail to check if the http server supports pipelining
I've just stumbled across this bug. It was rather difficult to identify. The effect (in my case) is that packages are listed as being from an untrusted source. Seems like that might warrant more than minor severity. The first two lines of the update are: Ign http://kite testing Release.gpg Hit http://kite testing/updates Release.gpg apt-get sends requests for both of these in the same packet and the server (dhttpd) sends back the first only (with no file name). apt-get assumes the data is for the second. So there is no signature for the testing Release file and its packages are marked untrusted. If the pipelining bug isn't worth fixing, perhaps a warning could be given that a file couldn't be found and it's one we might care about. Thanks! Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516864: libpam-afs-session: PAGs not used on SSH login
On Tue, Feb 24, 2009 at 09:08:57PM -0800, Russ Allbery wrote: david l goodrich d...@dsrw.org writes: It's a custom kernel, because it's a Xen domU. Which probably invites all kinds of pain. But its config file is used in a different Xen domU, which works fine. I've attached it, I'm not very adept at reading these files. It works for me, so I just copy it to my new systems and build the kernel with whatever version of gcc the new machine requires. Indeed, the kernel isn't built with keyring support: # # Security options # # CONFIG_KEYS is not set CONFIG_KEYS is the relevant setting. Now, that doesn't explain why it's working elsewhere, particularly if the same versions of everything are involved. In some ways, it raises more questions than it answers, such as how you're getting PAGs at all since the other way of doing them isn't exported in current kernels (but it may be that this is an older version). However, I suspect that if you enable CONFIG_KEYS and build an AFS kernel module against the resulting kernel, you'll find that this starts working. If I had to guess, I'd say that the AFS module is managing to create the group for the PAG but failing to hook into setgroups, so then when ssh calls setgroups, it blows away the PAG again and you lose access to your token. No idea why that isn't happening on your other systems too. It's likely that OpenAFS will completely drop support for kernels without keyring support in some future version, since doing anything else is just too ugly and is explicitly not supported by the Linux kernel developers. Success! Setting CONFIG_KEYS=y and rebuilding the kernel solved the problem: d...@chaos:~$ id uid=1000(dlg) gid=1000(dlg) groups=1000(dlg),1101353942 d...@chaos:~$ tokens Tokens held by the Cache Manager: User's (AFS ID 1000) tokens for a...@dsrw.org [Expires Feb 26 08:21] --End of list-- d...@chaos:~$ keyctl show Session Keyring -3 --alswrv 0 0 keyring: _ses.16448 12 s--v 0 0 \_ afs_pag: _pag d...@chaos:~$ Thanks so much for all your help, this has stumped me for quite some time. --david -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516864: libpam-afs-session: PAGs not used on SSH login
On Mon, Feb 23, 2009 at 08:53:37PM -0800, Russ Allbery wrote: david l goodrich d...@dsrw.org writes: Package: libpam-afs-session Version: 1.7-1 Severity: important When logging in via SSH, a user does not get AFS tokens or a PAG, but they do get kerberos tickets. This works correctly via the console, but not SSH. I suspect your PAM configuration is incorrect, since this works fine for me. Could you show me your auth and session PAM configuration? Certainly, they were taken from your README. chaos:~# grep -v ^# /etc/pam.d/common-auth auth [success=ok default=1] pam_krb5.so auth [default=done] pam_afs_session.so debug auth required pam_unix.so try_first_pass nullok_secure chaos:~# grep -v ^# /etc/pam.d/common-session session optional pam_krb5.so session required pam_afs_session.so debug chaos:~# Thank you! --david -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516864: libpam-afs-session: PAGs not used on SSH login
On Tue, Feb 24, 2009 at 12:55:35PM -0800, Russ Allbery wrote: david l goodrich d...@dsrw.org writes: Certainly, they were taken from your README. chaos:~# grep -v ^# /etc/pam.d/common-auth auth [success=ok default=1] pam_krb5.so auth [default=done] pam_afs_session.so debug auth required pam_unix.so try_first_pass nullok_secure chaos:~# grep -v ^# /etc/pam.d/common-session session optional pam_krb5.so session required pam_afs_session.so debug chaos:~# Hm, okay, that looks fine. I see that you have the debug flags added to pam_afs_session. When you connect with ssh, do you get log messages about pam_afs_session running? If so, what do you get? I sure do: - Feb 25 02:11:16 chaos sshd[18207]: Accepted password for dlg from 172.20.4.138 port 51178 ssh2 Feb 25 02:11:16 chaos sshd[18207]: pam_env(sshd:setcred): Unable to open env file: /etc/default/locale: No such file or directory Feb 25 02:11:16 chaos sshd[18207]: (pam_afs_session): pam_sm_setcred: entry (0x2) Feb 25 02:11:16 chaos sshd[18207]: (pam_afs_session): running /usr/bin/aklog as UID 1000 Feb 25 02:11:16 chaos sshd[18207]: (pam_afs_session): pam_sm_setcred: exit (success) Feb 25 02:11:16 chaos sshd[18207]: (pam_afs_session): pam_sm_open_session: entry (0x0) Feb 25 02:11:16 chaos sshd[18207]: (pam_afs_session): skipping, apparently already ran Feb 25 02:11:16 chaos sshd[18207]: (pam_afs_session): pam_sm_open_session: exit (success) Feb 25 02:11:16 chaos sshd[18212]: pam_env(sshd:setcred): Unable to open env file: /etc/default/locale: No such file or directory Feb 25 02:11:16 chaos sshd[18212]: (pam_afs_session): pam_sm_setcred: entry (0x2) Feb 25 02:11:16 chaos sshd[18212]: (pam_afs_session): skipping, apparently already ran Feb 25 02:11:16 chaos sshd[18212]: (pam_afs_session): pam_sm_setcred: exit (success) - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516864: libpam-afs-session: PAGs not used on SSH login
On Tue, Feb 24, 2009 at 06:49:10PM -0800, Russ Allbery wrote: david l goodrich d...@dsrw.org writes: running `id`, and looking for something like this (copied from a working ubuntu box): d...@aether:~$ id uid=1000(dlg) gid=1000(dlg) groups=106(admin),1000(dlg),1104162558 d...@aether:~$ The extra high-numbered group won't necessarily show up, since PAGs are really based on keyrings. If you run tokens, what is its output? oh, right, sorry. I am also running `tokens`. No dice. d...@chaos:~$ tokens Tokens held by the Cache Manager: --End of list-- d...@chaos:~$ keyctl show will also show you the underlying keyring of the PAG. I didn't know about keyctl, so I have no idea if this is a normal case for 'no PAGs': d...@chaos:~$ keyctl show Session Keyring -3: key inaccessible (Function not implemented) d...@chaos:~$ --david -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516864: libpam-afs-session: PAGs not used on SSH login
On Tue, Feb 24, 2009 at 07:11:01PM -0800, Russ Allbery wrote: david l goodrich d...@dsrw.org writes: On Tue, Feb 24, 2009 at 06:49:10PM -0800, Russ Allbery wrote: The extra high-numbered group won't necessarily show up, since PAGs are really based on keyrings. If you run tokens, what is its output? oh, right, sorry. I am also running `tokens`. No dice. d...@chaos:~$ tokens Tokens held by the Cache Manager: --End of list-- d...@chaos:~$ keyctl show will also show you the underlying keyring of the PAG. I didn't know about keyctl, so I have no idea if this is a normal case for 'no PAGs': d...@chaos:~$ keyctl show Session Keyring -3: key inaccessible (Function not implemented) d...@chaos:~$ That indicates you have no PAG indeed. You should normally get something like: windlord:~ keyctl show Session Keyring -3 --alswrv 0 0 keyring: _ses.3882 975847253: key inaccessible (Required key not available) Hm. Well, I'm stumped... this works fine for me with OpenSSH and PAM in a basically identical configuration, and your system logs say that the AFS PAM module thinks everything is working correctly and there are no problems. I'm not sure what else to try. Clearly there's something different about your system and your configuration that isn't happening on any of my systems, but I'm not sure what it could be. Could it be my ssh config? I'm really grasping at straws, here. This bug report was sort of my last resort grin I assume that if you run pagsh you then have a PAG, and if you run aklog inside that shell, you then have a token? Actually, the keyctl bit looks a bit off: d...@chaos:~$ pagsh sh-3.2$ id uid=1000(dlg) gid=1000(dlg) groups=1000(dlg),1101227443 sh-3.2$ aklog sh-3.2$ tokens Tokens held by the Cache Manager: User's (AFS ID 1000) tokens for a...@dsrw.org [Expires Feb 25 20:11] --End of list-- sh-3.2$ keyctl show Session Keyring -3: key inaccessible (Function not implemented) sh-3.2$ exit exit d...@chaos:~$ id uid=1000(dlg) gid=1000(dlg) groups=1000(dlg) d...@chaos:~$ tokens Tokens held by the Cache Manager: User's (AFS ID 1000) tokens for a...@dsrw.org [Expires Feb 25 21:28] --End of list-- d...@chaos:~$ keyctl show Session Keyring -3: key inaccessible (Function not implemented) d...@chaos:~$ --david -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516864: libpam-afs-session: PAGs not used on SSH login
On Tue, Feb 24, 2009 at 07:52:05PM -0800, Russ Allbery wrote: david l goodrich d...@dsrw.org writes: Could it be my ssh config? I'm really grasping at straws, here. This bug report was sort of my last resort grin Given that the PAM module is being run, it shouldn't be. UsePAM being set to no is the only thing I can think of there, and clearly it's not. Actually, the keyctl bit looks a bit off: d...@chaos:~$ pagsh sh-3.2$ id uid=1000(dlg) gid=1000(dlg) groups=1000(dlg),1101227443 sh-3.2$ aklog sh-3.2$ tokens Tokens held by the Cache Manager: User's (AFS ID 1000) tokens for a...@dsrw.org [Expires Feb 25 20:11] --End of list-- sh-3.2$ keyctl show Session Keyring -3: key inaccessible (Function not implemented) Oh, hm, you're right, I didn't notice the function not implemented part. Are you using the stock Debian kernel or did you build a custom kernel? And if you built a custom kernel, did you by chance build it without keyring support? I *think* the AFS module wouldn't even load in that case, but it may be that something weird is going on And if you have a kernel built with an exposed syscall table but no keyring support, I'm not entirely sure what the current AFS modules might do. Also, this is a regular system, yes, not a vserver or a Xen domU or user-mode Linux or some other unusual setup? It's a custom kernel, because it's a Xen domU. Which probably invites all kinds of pain. But its config file is used in a different Xen domU, which works fine. I've attached it, I'm not very adept at reading these files. It works for me, so I just copy it to my new systems and build the kernel with whatever version of gcc the new machine requires. --david # # Automatically generated make config: don't edit # Linux kernel version: 2.6.16.29-xenU # Tue Feb 24 02:03:42 2009 # CONFIG_X86_32=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION= # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set # CONFIG_IKCONFIG is not set # CONFIG_CPUSETS is not set CONFIG_INITRAMFS_SOURCE= CONFIG_UID16=y CONFIG_VM86=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 CONFIG_SLAB=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Block layer # # CONFIG_LBD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED=anticipatory # # Processor type and features # # CONFIG_X86_PC is not set CONFIG_X86_XEN=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set CONFIG_M686=y # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_TSC=y CONFIG_SMP=y CONFIG_SMP_ALTERNATIVES=y CONFIG_NR_CPUS=8 CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y # CONFIG_TOSHIBA
Bug#516864: libpam-afs-session: PAGs not used on SSH login
Package: libpam-afs-session Version: 1.7-1 Severity: important When logging in via SSH, a user does not get AFS tokens or a PAG, but they do get kerberos tickets. This works correctly via the console, but not SSH. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.16.29-xenU (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages libpam-afs-session depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libkrb53 1.6.dfsg.4~beta1-6 MIT Kerberos runtime libraries ii libpam0g 1.0.1-5Pluggable Authentication Modules l Versions of packages libpam-afs-session recommends: ii libpam-krb53.11-4PAM module for MIT Kerberos ii openafs-client 1.4.7.dfsg1-6 AFS distributed filesystem client ii openafs-krb5 1.4.7.dfsg1-6 AFS distributed filesystem Kerbero libpam-afs-session suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#447580: dhttpd: Man page and usage message are not complete
It also appears there's a -b option. Here's a snippet to add to the man page (didn't seem worth a patch, just paste it wherever). .TP .B \-b IP address Listen on specified interface. Defaults to 0.0.0.0 (all interfaces). Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#489544: installation-reports
Hi Jérémy, sorry to have taken so long to get back! I had to give my brother the flash drive, and only recently got another one to test with. I tried this installation again with a daily build: == Daily build #3 for i386, using installer build from sid == This build finished at Sat Jan 17 15:10:11 UTC 2009. The problem still stands -- /scripts/local-top/cryptroot does not wait for its cryptsource, and reaches here: message cryptsetup: source device $cryptsource not found return 1 I guess the assumption is that udev_settle would find the device, but it seems not to -- udev_settle considers itself finished *before* all the USB devices have been detected, so udev_settle isn't doing what we expect in this case. As requested, here are the versions: ii cryptsetup2:1.0.6-7 ii initramfs-tools 0.92o Cheers, David On Wed 30 Jul 2008 2:21 am, Jérémy Bobbio wrote: On Wed, Jul 30, 2008 at 12:47:02AM -0700, David L. Emerson wrote: I've just finished a similar installation with the Lenny beta 2 installer (encrypted lvm on bootable usb flash drive) Thanks. I would have been more happy if you would have used a daily build, but it's great nevertheless. re Problem 3: STILL A BIG PROBLEM. Here are the boot messages: Uncompressing Linux... Ok, booting the kernel. Loading, please wait... Volume group socrates not found Setting up cryptographic volume sda2_crypt (based on /dev/sda2) cryptsetup: Source device /dev/sda2 not found [... wait about 5 seconds ...] sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Assuming drive cache: write through [... forehead - desk ...] [... wait about a minute, then it drops to busybox because the /dev/mapper/socrates-root_vol does not exist ...] so, it looks like I will have to manually reroll the initramfs again. If you want me to test again with a later version, I'll try and figure out a way to do that :) Could you give me the installed version of the initramfs-tools and cryptsetup packages? I have seen similar issues being fixed in recent version of those packages, and I am not sure if they have migrated to Lenny yet. (The development version of debian-installer installs testing by default.) Cheers, -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509235: iceweasel crashes when libcurl3-gnutls is not installed
This was a problem on my brother's computer, and it doesn't look like I'm going to have an opportunity to test it again until I upgrade my own system to Lenny. ~David. On Friday 19 December 2008 11:44 pm, Mike Hommey wrote: On Fri, Dec 19, 2008 at 07:27:31PM -0800, David L. Emerson wrote: Package: iceweasel Version: 3.0.4-1 Severity: important *** Please type your report below this line *** After logging into gmail, the inbox page mostly loads and displays, but then iceweasel completely crashes. I did an strace, which showed that it was looking for libcurl-gnutls, and then killed by sigsegv So I installed libcurl3-gnutls and now iceweasel/gmail works fine. the iceweasel package should have a mandatory dependency on libcurl3-gnutls, if the absence makes it crash like that :) Remove libcurl3-gnutls, then try running MOZ_DISABLE_PLUGINS=1 iceweasel -safe-mode My bet is that it will stop crashing. That's not iceweasel requiring curl-gnutls, but something else you installed. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#507161: experiencing segmentation fault, no sound
Skype (not running) works with the sound system just butifully. However, I get no sound when playing etoys and get crashes instead. Some scripts crash immediately, others grant me a little while. AMD64 issue? I have this problem when running the first demo (Welcome.pr) on AMD64. It works on i386 (with sound). Thanks! Dave -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509235: iceweasel crashes when libcurl3-gnutls is not installed
Package: iceweasel
Version: 3.0.4-1
Severity: important
*** Please type your report below this line ***
After logging into gmail, the inbox page mostly loads and displays, but
then iceweasel completely crashes.
I did an strace, which showed that it was looking for libcurl-gnutls,
and then killed by sigsegv
So I installed libcurl3-gnutls and now iceweasel/gmail works fine.
the iceweasel package should have a mandatory dependency on
libcurl3-gnutls, if the absence makes it crash like that :)
Here is the last 75 lines of strace iceweasel:
open(/home/bop/.mozilla/firefox/wz8lokww.default/prefs.js, O_RDONLY) =
61
close(61) = 0
open(/usr/lib/iceweasel/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/mozilla-firefox/plugins/libcurl.so.4, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 61
fstat64(61, {st_mode=S_IFREG|0644, st_size=45364, ...}) = 0
mmap2(NULL, 45364, PROT_READ, MAP_PRIVATE, 61, 0) = 0xae996000
close(61) = 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i686/cmov/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/lib/i686/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/lib/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/lib/i686/cmov/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/i686/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/usr/lib/sse2/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/usr/lib/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/lib/i486-linux-gnu/libcurl.so.4, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/i486-linux-gnu/libcurl.so.4, O_RDONLY) = -1 ENOENT (No
such file or directory)
munmap(0xae996000, 45364) = 0
open(/usr/lib/iceweasel/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/lib/mozilla-firefox/plugins/libcurl-gnutls.so.4, O_RDONLY)
= -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 61
fstat64(61, {st_mode=S_IFREG|0644, st_size=45364, ...}) = 0
mmap2(NULL, 45364, PROT_READ, MAP_PRIVATE, 61, 0) = 0xae996000
close(61) = 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i686/cmov/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/lib/i686/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/lib/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/lib/i686/cmov/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/lib/i686/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/sse2/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/lib/i486-linux-gnu/libcurl-gnutls.so.4, O_RDONLY) = -1 ENOENT
(No such file or directory)
open(/usr/lib/i486-linux-gnu/libcurl-gnutls.so.4, O_RDONLY) = -1
ENOENT (No such file or directory)
munmap(0xae996000, 45364) = 0
open(/usr/lib/iceweasel/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/mozilla-firefox/plugins/libcurl.so.3, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 61
fstat64(61, {st_mode=S_IFREG|0644, st_size=45364, ...}) = 0
mmap2(NULL, 45364, PROT_READ, MAP_PRIVATE, 61, 0) = 0xae996000
close(61) = 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/i686/cmov/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/lib/i686/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/lib/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/usr/lib/i686/cmov/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/i686/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/usr/lib/sse2/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such file
or directory)
open(/usr/lib/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such file or
directory)
open(/lib/i486-linux-gnu/libcurl.so.3, O_RDONLY) = -1 ENOENT (No such
file or directory)
open(/usr/lib/i486-linux-gnu/libcurl.so.3, O_RDONLY) = -1 ENOENT (No
such file or directory)
munmap(0xae996000, 45364) = 0
open(/usr/lib/iceweasel/libcurl-gnutls.so.3, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/usr/lib/mozilla-firefox/plugins/libcurl-gnutls.so.3, O_RDONLY)
= -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 61
fstat64(61, {st_mode=S_IFREG|0644, st_size=45364, ...}) = 0
mmap2(NULL, 45364, PROT_READ, MAP_PRIVATE, 61, 0) = 0xae996000
close(61)
Bug#486507: libx11-6: VMWare Server sees X responses out of order
Julien Cristau wrote: It would be nice to get some feedback on this from the people who can reproduce the issue. This means either getting a backtrace from the failing assert(), with debug packages for libxcb and libx11 installed, or upgrading libx11-6 to the version in experimental, which uses the work mentioned above. I think I can reproduce it. I think I can install the debug packages for libxcb and libx11. What are the steps to get the right backtrace? Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493572: kwin: intermittent: window decorations and title bars are absent
I was finally able to get to this computer, and I am still seeing the intermittent bug with the versions you mentioned: kdebase 4:3.5.9.dfsg.1-5 kdelibs 4:3.5.9.dfsg.1-6 ~David. On Friday 08 August 2008 1:10 pm, Ana Guerrero wrote: On Sun, Aug 03, 2008 at 03:10:05AM -0700, David L. Emerson wrote: Package: kwin Version: 4:3.5.9.dfsg1-(4?) Severity: important sometimes when I start kde, there are no title bars (and thus no window decorations) on any of the windows. Additionally, I have only one virtual desktop instead of four, and it seems like some of the key bindings do not work. This is an intermittent problem, but I see it pretty frequently: once every 2 or 3 times I start kde. Usually I can make the problem go away by ending my session and starting a new one. I have a fresh installation of debian lenny and kde 3.5.9 with an empty home directory. I selected all the defaults while going through the kde theming wizard. according to the kde team: Distribution issue. Please report this to the Debian team. http://bugs.kde.org/show_bug.cgi?id=168179 (sorry for the lack of detailed info; I'm not on the lenny box right now, but I did update it 3 days ago.) -- System Information: Debian Release: lenny/sid APT prefers lenny Architecture: i386 (i686) You are skipping the info of the available package versions isntalled on your system. Does this problem occurs if you have your system up-to-date? With kdebase 4:3.5.9.dfsg.1-5 and kdelibs 4:3.5.9.dfsg.1-6. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493572: kwin: intermittent: window decorations and title bars are absent
Package: kwin Version: 4:3.5.9.dfsg1-(4?) Severity: important sometimes when I start kde, there are no title bars (and thus no window decorations) on any of the windows. Additionally, I have only one virtual desktop instead of four, and it seems like some of the key bindings do not work. This is an intermittent problem, but I see it pretty frequently: once every 2 or 3 times I start kde. Usually I can make the problem go away by ending my session and starting a new one. I have a fresh installation of debian lenny and kde 3.5.9 with an empty home directory. I selected all the defaults while going through the kde theming wizard. according to the kde team: Distribution issue. Please report this to the Debian team. http://bugs.kde.org/show_bug.cgi?id=168179 (sorry for the lack of detailed info; I'm not on the lenny box right now, but I did update it 3 days ago.) -- System Information: Debian Release: lenny/sid APT prefers lenny Architecture: i386 (i686) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493322: aptitude: pressing 'escape' in search/tree limit dialog should cancel
Package: aptitude Version: 0.4.11.8-1 Severity: normal Pressing 'escape' in the dialog puts a ^[ into the search term, instead of just closing/canceling the search/limit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493320: aptitude: pressing 'delete' in search/tree limit dialog doesn't delete previous entry
Package: aptitude Version: 0.4.11.8-1 Severity: normal There's a great new feature where '/' search and 'l' limit bring up a dialog that keeps the previous search. It's also really great that if I type something, that previous search is deleted. However, suppose I bring up the dialog and I just want to clear out the tree limit, and show everything again. If I press the delete key while the dialog is showing the previous entry, it does not delete anything. If I press 'end' and backspace, I can delete it. But it would be nice to use the 'delete' key as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489544: installation-reports
I've just finished a similar installation with the Lenny beta 2 installer (encrypted lvm on bootable usb flash drive) re Problem 1: I was able to delete the swap partition with your advise: deleting both partitions, then the volumes, then making one volume. Kinda cumbersome ... I guess it would be nice if there was a prompt about swap vs. no swap, but it's also nice not to bother most people with it. re Problem 2: this time I didn't dd my drive ahead of time, I just let the installer do its thing :P re Problem 3: STILL A BIG PROBLEM. Here are the boot messages: Uncompressing Linux... Ok, booting the kernel. Loading, please wait... Volume group socrates not found Setting up cryptographic volume sda2_crypt (based on /dev/sda2) cryptsetup: Source device /dev/sda2 not found [... wait about 5 seconds ...] sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Assuming drive cache: write through [... forehead - desk ...] [... wait about a minute, then it drops to busybox because the /dev/mapper/socrates-root_vol does not exist ...] so, it looks like I will have to manually reroll the initramfs again. If you want me to test again with a later version, I'll try and figure out a way to do that :) ~David. On Monday 28 July 2008 9:50 am, Jérémy Bobbio wrote: On Sun, Jul 06, 2008 at 01:21:00PM -0700, David L. Emerson wrote: Image version: debian-40r3-i386-netinst.iso […] This computer supports booting from USB, so I decided to install debian on a USB Flash drive. I wanted an encrypted root partition. PROBLEM 1. I first tried the automatic encrypted LVM setup. It insisted upon making a swap partition, and I was unable to delete that partition. Of course I don't want a swap partition on a flash based drive. I ultimately had to back up several steps and do a manual setup. The automatic encrypted LVM setup create the swap partition as a Logical Volume. The easiest (but not obvious) way to get rid of it would have been to: * go to Configure the Logical Volume Manager, * remove both Logical Volumes (swap_1 and root), * create a new Logical Volume (root), * apply those changes, * configure the newly created Logical Volume (root) as / We could probably manage to detect that we are partitioning a Solid State Device, and skip the creation of a swap partition, but this would require a fair amount of changes in partman. I doubt anyone will be working on that in the d-i team, but patches are more than welcome. PROBLEM 2. Before I started the install, I used dd if=/dev/urandom of=/dev/sda to write random data to the drive, which makes cracking an encrypted partition/drive much more difficult. However, the debian installer insisted on writing (zeros?) to the to-be-encrypted partition before formatting. This was very time consuming, wasteful/redundant, and perhaps a security liability as well. In fact, the installer did this several times due to problem 1 ;) I should be able to skip that writing since I already did it myself. The installer is not writing zeros. It is actually doing a similar process than the one you did by yourself! :) It can be avoided though when using manual partitioning, by switching Erase data to no while configuring the partition used as physical volume for encryption. PROBLEM 3. System would not boot!! . It brought up the grub menu just fine, and began loading the kernel and initramfs. The problem occured when it tried to configure lvm (/usr/share/initramfs-tools/scripts/local-top/lvm) -- the kernel had not yet detected the presence of the USB Flash drive! Thus the call to activate_vg $ROOT was doomed to failure, since udev had not yet discovered the root device. A few seconds after the failure messages, udev discovered the device -- udev had settled before running local-top, but the USB event came later. […] AFAIK, a lot of related issues have been fixed for Lenny. If you could give it a try, it would be great. Cheers, -- Jérémy Bobbio .''`. [EMAIL PROTECTED] : :Ⓐ : # apt-get install anarchism `. `'` `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489544: installation-reports
Package: installation-reports Boot method: CD Image version: debian-40r3-i386-netinst.iso Date: 2008 June 6 Machine: IBM Thinkpad T42 Processor: Pentium M 1.8 GHz Memory: 1.5 GB Partitions: installed on an unpartitioned 4 GB USB flash drive Output of lspci -knn (or lspci -nn): (irrelevant) Base System Installation Checklist: (all OK except as noted below) Comments/Problems: This computer supports booting from USB, so I decided to install debian on a USB Flash drive. I wanted an encrypted root partition. PROBLEM 1. I first tried the automatic encrypted LVM setup. It insisted upon making a swap partition, and I was unable to delete that partition. Of course I don't want a swap partition on a flash based drive. I ultimately had to back up several steps and do a manual setup. PROBLEM 2. Before I started the install, I used dd if=/dev/urandom of=/dev/sda to write random data to the drive, which makes cracking an encrypted partition/drive much more difficult. However, the debian installer insisted on writing (zeros?) to the to-be-encrypted partition before formatting. This was very time consuming, wasteful/redundant, and perhaps a security liability as well. In fact, the installer did this several times due to problem 1 ;) I should be able to skip that writing since I already did it myself. PROBLEM 3. System would not boot!! . It brought up the grub menu just fine, and began loading the kernel and initramfs. The problem occured when it tried to configure lvm (/usr/share/initramfs-tools/scripts/local-top/lvm) -- the kernel had not yet detected the presence of the USB Flash drive! Thus the call to activate_vg $ROOT was doomed to failure, since udev had not yet discovered the root device. A few seconds after the failure messages, udev discovered the device -- udev had settled before running local-top, but the USB event came later. In order to solve this problem, I added a script to /etc/initramfs-tools/scripts/init-premount that waits for the device to appear in the /dev tree: echo -n Waiting for /dev/sda5 to appear while ! [ -b /dev/sda5 ]; do echo -n .; sleep 1s; done It took me several days to figure out what the problem was, how to fix it, and how to use initramfs to roll the initrd, but now it works! Although my script could probably be more robust. IMO, the debian-installer should always set up the init system to wait for the $ROOT (and $resume?) partitions to be visible in the /dev tree before proceeding with the local-top scripts. ~David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469095: Wifi led does not turns on
There's a discussion of this bug and patches at: http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1209 Probably this should be reassigned to the kernel. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467059: /usr/bin/apt-get: dist-upgrade [sid] gets internal error re: tzdata
Package: apt Version: 0.7.6 Severity: important File: /usr/bin/apt-get Last five messages issued prior to termination: 634 upgraded, 95 newly installed, 3 to remove and 0 not upgraded. Need to get 0B/703MB of archives. After unpacking 261MB of additional disk space will be used. Do you want to continue [Y/n]? E: Internal Error, Could not perform immediate configuration (2) on tzdata -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture i386; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends 0; APT::Install-Suggests 0; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^linux-image.*; APT::NeverAutoRemove:: ^linux-restricted-modules.*; APT::Periodic ; APT::Periodic::Update-Package-Lists 1; APT::Periodic::Download-Upgradeable-Packages 0; APT::Archives ; APT::Archives::MaxAge 30; APT::Archives::MinAge 2; APT::Archives::MaxSize 500; APT::Authentication ; APT::Authentication::TrustCDROM true; APT::Acquire ; APT::Acquire::Translation environment; Dir /; Dir::State var/lib/apt/; Dir::State::lists lists/; Dir::State::cdroms cdroms.list; Dir::State::userstatus status.user; Dir::State::status /var/lib/dpkg/status; Dir::Cache var/cache/apt/; Dir::Cache::archives archives/; Dir::Cache::srcpkgcache srcpkgcache.bin; Dir::Cache::pkgcache pkgcache.bin; Dir::Etc etc/apt/; Dir::Etc::sourcelist sources.list; Dir::Etc::sourceparts sources.list.d; Dir::Etc::vendorlist vendors.list; Dir::Etc::vendorparts vendors.list.d; Dir::Etc::main apt.conf; Dir::Etc::parts apt.conf.d; Dir::Etc::preferences preferences; Dir::Bin ; Dir::Bin::methods /usr/lib/apt/methods; Dir::Bin::dpkg /usr/bin/dpkg; Unattended-Upgrade ; Unattended-Upgrade::Allowed-Origins ; Unattended-Upgrade::Allowed-Origins:: Debian stable; DPkg ; DPkg::Pre-Install-Pkgs ; DPkg::Pre-Install-Pkgs:: /usr/sbin/dpkg-preconfigure --apt || true; DPkg::Post-Invoke ; DPkg::Post-Invoke:: if [ -d /var/lib/update-notifier ]; then touch /var/lib/update-notifier/dpkg-run-stamp; fi; Acquire ; Acquire::http ; Acquire::http::Proxy false; -- (no /etc/apt/preferences present) -- -- /etc/apt/sources.list -- deb ftp://debian.lcs.mit.edu/debian/ sid main contrib non-free deb-src ftp://debian.lcs.mit.edu/debian/ sid main contrib non-free # deb ftp://techweb.rfa.org/debian/ sid main contrib non-free # deb-src ftp://techweb.rfa.org/debian/ sid main contrib non-free # deb ftp://ftp.gtlib.gatech.edu/pub/debian/ sid` main contrib non-free # deb-src ftp://ftp.gtlib.gatech.edu/pub/debian/ sid main contrib non-free # deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 Binary-1 (20060710)]/ etch main # deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 Binary-1 (20060710)]/ etch main # deb http://techweb.rfa.org/debian/ etch main # deb-src http://techweb.rfa.org/debian/ etch main # deb ftp://techweb.rfa.org/debian/ etch main # deb-src ftp://techweb.rfa.org/debian/ etch main # deb http://security.debian.org/ etch/updates main # deb-src http://security.debian.org/ etch/updates main -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apt depends on: ii debian-archive-keyring2007.07.31 GnuPG archive keys of the Debian a ii libc6 2.6.1-3GNU C Library: Shared libraries ii libgcc1 1:4.2.1-5 GCC support library ii libstdc++64.2.1-5The GNU Standard C++ Library v3 apt recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459599: greylistd: an hour is not 600 seconds
fixed 459599 0.8.6 thanks in /etc/greylistd/config there is this comment: # Default is 1 hour = 600 seconds but an hour is not 600 seconds but 3600 seconds instead This problem does not exist in version 0.8.6 (maybe when the default was changed to 10 minutes) so this bug can probably be closed. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463657: frozen-bubble: Menu doesn't work.
Package: frozen-bubble Version: 2.1.0-2 Severity: normal When frozen-bubble is installed the command in the menu is frozen-bubble, which doesn't work. Changing it to /usr/games/frozen-bubble solves the problem. Shouldn't the menu be installed with the full path? Thanks! Dave -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages frozen-bubble depends on: ii fb-music-high 0.1.2High quality, large music files fo ii frozen-bubble-data 2.1.0-2 Data files for Frozen-Bubble ii libc6 2.7-6GNU C Library: Shared libraries ii libglib2.0-02.14.5-2 The GLib library of C routines ii libpango1.0-0 1.18.4-1 Layout and rendering of internatio ii libsdl-mixer1.2 1.2.8-3 mixer library for Simple DirectMed ii libsdl-pango1 0.1.2-4 text rendering with Pango in SDL a ii libsdl-perl 1.20.3dfsg-3 SDL bindings for the Perl language ii libsdl1.2debian 1.2.13-1 Simple DirectMedia Layer ii perl5.8.8-12 Larry Wall's Practical Extraction ii perl-base [perlapi-5.8.8] 5.8.8-12 The Pathologically Eclectic Rubbis frozen-bubble recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462712: exim4-base: exim_db(8) missing paragraph break.
Package: exim4-base Version: 4.68-2 Severity: minor In the exim_db man page there are 3 term paragraphs for the 3 databases. After the last (misc) there is no paragraph break so the rest of the description section is indented too far. I'm not that quick at making patches but all that is needed is to change line 48 from blank to .P in exim4-4.68/debian/manpages/exim_db.8. Thanks! Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409350: greylistd: exim4 config acl error (senders = : means bounce list excluded!)
In version 0.8.6 besides the acl_check_rcpt there's acl_check_data, which runs the greylist check at data time for . So it seems that bounces will get checked, just at data time rather than rcpt time. Does that solve the problem? Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
